fix: make release workflow resilient to version desync#40
Merged
Conversation
Add git pull --rebase at two points: 1. Before version bump — picks up previous release's version commit 2. Before git push — handles any commits pushed during the job This prevents the scenario where a queued release job bumps from a stale version and collides with an already-published npm version. Co-Authored-By: Claude Opus 4.6 <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
Add
git pull --rebaseat two critical points in the release workflow:npm version patchstarts from the correct baseCombined with the concurrency group from PR #38, this makes the release pipeline resilient to rapid consecutive merges.
Test plan
🤖 Generated with Claude Code