docs: record the v0.5.3 stale-tag incident (git pull before tagging) - #54
Merged
Conversation
git checkout main reports "up to date with origin/main" against the last-fetched local tracking ref — it does not implicitly fetch. After merging a PR from a different local branch (the normal flow here), local main can silently sit behind origin/main. Tagging that stale HEAD ships a release missing the fix it claims to contain, with every quality gate still green (they run against the older, still-valid code that got tagged). Happened for real: v0.5.3 was first tagged one PR short of its own fix, had to be deleted and retagged after an explicit git pull. Recorded in make-space.md §8 so the next release doesn't repeat it. Co-Authored-By: Claude Sonnet 5 <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
v0.5.3was first tagged from a stale localmain— one PR short of the fix it was supposed to ship — becausegit checkout mainreports "up to date" against the last-fetched tracking ref without implicitly fetching. Every quality gate stayed green since they ran against the (older, still valid) code that actually got tagged. Had to delete and retag after an explicitgit pull.Records the incident and the fix (
git pull origin mainbefore tagging, sanity-checkgit logagainstorigin/mainpost-fetch) inmake-space.md§8 so it doesn't happen again.Test plan