Skip to content

fix(ci): use annotated tags in release workflow - #13

Merged
antosubash merged 1 commit into
mainfrom
claude/funny-saha
Mar 27, 2026
Merged

antosubash merged 1 commit into
mainfrom
claude/funny-saha

Conversation

@antosubash

Copy link
Copy Markdown
Owner

Summary

  • Use annotated tags (git tag -a) instead of lightweight tags so --follow-tags actually pushes them to the remote
  • Check out by tag ref instead of SHA in the github-release job so --verify-tag can find the tag

Root cause

git push origin main --follow-tags only pushes annotated tags. The workflow was creating lightweight tags, so the tag never reached the remote — causing gh release create --verify-tag to fail.

Test plan

  • Trigger a release via workflow_dispatch and verify the tag is pushed and GitHub Release is created

🤖 Generated with Claude Code

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>
@antosubash
antosubash merged commit ae17ad0 into main Mar 27, 2026
2 checks passed
@antosubash
antosubash deleted the claude/funny-saha branch March 27, 2026 09:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant