Repository navigation
docs(release): push the version tag by name, not every local tag - #736
Merged
Merged
Conversation
Step 11 prescribed `git push --tags`, which pushes every tag in the local repo. Cutting v6.8.0 carried up a stray `pre-rebase-251256b9` backup tag that had been sitting locally since May, publishing it to the public repo alongside the release. Both the doc and the /release skill now push the single tag by name. The comment records the v6.8.0 incident so the next person does not "simplify" it back. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WdKpn9PEjXtYiyRoG3Y7or
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.
Cutting v6.8.0 published a stray tag. Step 11 of the release flow prescribes
git push --tags, which pushes every tag in the local repo, not just the one just created:pre-rebase-251256b9was a local backup tag from May 2026 that had never been pushed. It is now deleted from the remote, and this stops the next release recreating the problem.Change
docs/RELEASING.mdstep 11 and the matching step 9 in.claude/skills/release/SKILL.mdboth become:git push && git push origin vX.Y.ZBoth carry a comment naming the v6.8.0 incident, so the shorter form does not get restored as a tidy-up later.
Scope
git push --tagsappeared in exactly two places repo-wide, both fixed here.scripts/tag-plugins.shwas already correct — it pushes each native plugin tag by name.Note on the deleted tag
Checked before deleting: the commit
251256b9was an ancestor of no branch and referenced by no other tag, so that tag was its only reference. The work it backed up ("readdesktop_notificationsfrom env var, notuser_configsubstitution") did survive its rebase and is live onmain—plugins/arckit-claude/hooks/notify-stale-artifacts.mjs:39readsCLAUDE_PLUGIN_OPTION_DESKTOP_NOTIFICATIONS, and the plugin CHANGELOG records it. Nothing unique was lost.🤖 Generated with Claude Code
https://claude.ai/code/session_01WdKpn9PEjXtYiyRoG3Y7or