Repository navigation
ci(release): restore annotated tag before validation - #10
Merged
Merged
Conversation
actions/checkout@v4 fetches the pushed tag as +<sha>:refs/tags/<tag>, replacing the annotated tag with a lightweight ref, so the annotated-tag check rejected every real release tag. Force-fetch the tag object by name before validating it. Co-Authored-By: Claude Opus 5.5 (1M context) <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.
Problem
The
v0.15.0release run failed at the annotated-tag check even though the pushed tag is annotated.actions/checkout@v4fetches the tag as+<sha>:refs/tags/v0.15.0, replacing the annotated tag object with a lightweight ref, sogit cat-file -treportscommit.Fix
Force-fetch the tag object by name right after checkout, before validation.
Verification
Reproduced the checkout fetch sequence in a scratch clone against the published
v0.15.0tag:git cat-file -treturnedcommitafter checkout andtagafter the restore step, still peeling to the tagged commit. Workflow YAML parses.Nothing was published by the failed run; after merge,
v0.15.0is re-pointed to the merge commit.🤖 Generated with Claude Code