chore(release): refresh local binary as a final release step#31
Merged
chore(release): refresh local binary as a final release step#31
Conversation
Add step 11 to the release skill: after the GitHub Actions workflow succeeds, run `specflow self-update` (or fall back to a manual replace when self-update itself is what we just fixed) so the local binary matches what we just shipped. The release workflow publishes to GitHub Releases — it does not push to the local machine. The only auto-update channel is `specflow self-update` invoked locally, and forgetting to run it after each release silently leaves the local install behind. v0.7.1 stayed installed through v0.7.2/0.7.3/0.7.4 until the next qa-tester dispatch caught the drift. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds step 11 to the release skill: after the GitHub Actions workflow turns green, run
specflow self-update(or fall back to a manual replace when the bug we just fixed is self-update itself) so~/.local/bin/specflowends up on the version we just published.Why
The release workflow publishes to GitHub Releases — it does not push to Kevin's machine. The only auto-update channel is
specflow self-updateinvoked locally. Skipping that step after each release silently leaves the local install behind, which defeats the qa-tester loop (T0 in the catalogue runs against whatever's on PATH).Concrete proof this gap was real: v0.7.1 stayed installed through v0.7.2 (which fixed self-update), v0.7.3, and v0.7.4. The next qa-tester dispatch caught it — but only because the abort-BLOCKER triggered before any test ran. The 0.7.1 binary couldn't even self-update past its own bug, so a manual replace of
~/.local/bin/specflowwas needed to break the deadlock.What changed
.claude/skills/release/SKILL.mdwithself-updateas the happy path and a checksum-verified manual-replace fallback.No product code touched.
Test plan
specflow-macos-arm64v0.7.4, verified checksum4394af6d..., replaced~/.local/bin/specflow, confirmedspecflow --version→0.7.4).self-updateon an already-fixed binary).🤖 Generated with Claude Code