ci(publish): atomic branch+tag push with race retry#198
Merged
Conversation
--follow-tags pushes per-ref: when a merge train moves main mid-run, the HEAD:main push is rejected but the tag ref still lands, orphaning a release tag that fails every later run with 'tag already exists' (v0.43.25 and v0.43.27 today). --atomic makes branch+tag land together or not at all; a lost race resets to fresh main and retries.
tangletools
approved these changes
Jul 15, 2026
tangletools
left a comment
tangletools
left a comment
There was a problem hiding this comment.
✅ Auto-approved drewstone PR — 77acac7c
This PR was opened by the trusted drewstone account.
The full PR reviewer audit still runs separately and will publish findings if it detects issues.
tangletools · auto-approval · reason: drewstone_author · 2026-07-15T19:55:20Z
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
2 participants
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.
Kills the orphaned-release-tag class at the root:
--follow-tagsis per-ref, so a merge train racing the auto-release leaves the tag accepted while HEAD:main is rejected — v0.43.25 and v0.43.27 both orphaned today, each blocking all subsequent releases until manual tag deletion.--atomiclands branch+tag together or not at all; on a lost race the job resets to fresh main and retries (the newer merge's queued run then no-ops via the already-published check). Filename stays publish.yml (npm OIDC trust is filename-bound).