Skip to content

Make the confirm step pasteable and run it from the right branch - #53

Merged
Danathar merged 1 commit into
mainfrom
docs/pasteable-confirm-step
Aug 26, 2026
Merged

Make the confirm step pasteable and run it from the right branch#53
Danathar merged 1 commit into
mainfrom
docs/pasteable-confirm-step

Conversation

@Danathar

Copy link
Copy Markdown
Owner

Two failures found by actually following the release procedure for v0.9.1.

1. The command was not pasteable

git pull && python3 homebrew_formula.py --check   # → "pin is current."

Interactive zsh does not treat # as a commentINTERACTIVE_COMMENTS is off by default — so pasting this passed the comment to the script as arguments:

homebrew_formula.py: error: unrecognized arguments: # → pin is current.

The expected output is prose now rather than an inline comment. A scan confirms it was the only such comment in any pasteable block across all five markdown files.

2. It ran on the wrong branch

git pull with no switch — but step 3 leaves you on the release branch. Pulling there reports Already up to date while the bot's formula commit sits on main:

75a898b..1f55375  main  -> origin/main
Already up to date.

So --check would read a stale formula from the release branch and the confirmation would be meaningless — worse than not checking, because it looks like it passed.

Now

git switch main && git pull
python3 homebrew_formula.py --check

It should print Homebrew formula pin is current.

Verified by running the corrected sequence from a release-branch checkout: prints exactly that, exit 0.

609 tests pass.

🤖 Generated with Claude Code

Two failures hit while actually following the release procedure.

The line carried a trailing `# → "pin is current."` comment. Interactive zsh
does not treat `#` as a comment -- INTERACTIVE_COMMENTS is off by default --
so pasting it passed the comment to the script as arguments:

    homebrew_formula.py: error: unrecognized arguments: # → pin is current.

The expected output is prose now rather than an inline comment. It was the
only such comment in any pasteable block across the docs.

The command was also `git pull` with no branch switch, but step 3 leaves you
on the release branch. Pulling there reports "Already up to date" while the
bot's formula commit sits on main, so --check reads a stale formula and the
whole confirmation is meaningless. It switches to main first, and says why.

Verified by running the corrected sequence from a release branch checkout.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@Danathar
Danathar merged commit 2a4f226 into main Aug 26, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant