Repository navigation
fix(ci): use annotated tags in release workflow - #13
Merged
Merged
Conversation
Lightweight tags created by `git tag` are not pushed by `--follow-tags`, causing `--verify-tag` to fail in the github-release job. Switch to annotated tags and check out by tag ref instead of SHA. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2 of 5 tasks
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
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
git tag -a) instead of lightweight tags so--follow-tagsactually pushes them to the remotegithub-releasejob so--verify-tagcan find the tagRoot cause
git push origin main --follow-tagsonly pushes annotated tags. The workflow was creating lightweight tags, so the tag never reached the remote — causinggh release create --verify-tagto fail.Test plan
workflow_dispatchand verify the tag is pushed and GitHub Release is created🤖 Generated with Claude Code