fix(ci): gate Registry/version-tagged jobs on actual new tag#15
Merged
Conversation
The release job used `gh release view "v$VERSION"` to decide whether a release happened, which always returned true once any release matched the package.json version. That's a permanent yes here because branch protection silently blocks the @semantic-release/git push to main, so package.json drifts from the published tags. Switched to a tag-diff check: capture `git describe --tags` before semantic-release, compare after. This is bulletproof against the package.json drift and signals a release ONLY when a new tag was just created. Side effects of the better signal: - `mcp-registry` job stops trying to re-publish duplicate versions on chore(deps)/no-release pushes. - Docker now tags `:latest` and `:sha-<short>` on every main push (so ACA picks up dependency bumps), and `:vX.Y.Z` only when a real release happened. Refs: mcp-registry-publish-gating skill.
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
The release job used `gh release view "v$VERSION"` to decide whether a release happened, which always returned true once any release matched the `package.json` version. That's a permanent yes in this fleet because branch protection silently blocks the `@semantic-release/git` push to main, so `package.json` drifts from the published tags.
Switched to a tag-diff check: capture `git describe --tags --abbrev=0` before semantic-release, compare after. Authoritative — signals a release ONLY when a new tag was just created.
What this unblocks
Refs
Test plan