Skip to content

fix(ci): push tags explicitly for GitHub Release creation#24

Merged
henrypalacios merged 1 commit intomainfrom
fix/tag-push-explicit
Apr 17, 2026
Merged

fix(ci): push tags explicitly for GitHub Release creation#24
henrypalacios merged 1 commit intomainfrom
fix/tag-push-explicit

Conversation

@henrypalacios
Copy link
Copy Markdown
Collaborator

Summary

Replace git push --follow-tags with explicit tag push. Tags with slashes (protocol-core/v0.1.1) are not pushed by --follow-tags, causing gh release create to fail with "tag exists locally but has not been pushed".

Root cause

git push --follow-tags only pushes tags that are reachable from the pushed refs AND are annotated. Our tags are lightweight and contain /, which --follow-tags doesn't handle reliably.

Test plan

  • Re-run publish workflow — tag should be pushed and GitHub Release created

Tags with slashes (protocol-core/v0.1.1) are not pushed by
git push --follow-tags. Push branch and tag separately to ensure
the tag exists on remote before gh release create runs.
@henrypalacios henrypalacios merged commit fc24c42 into main Apr 17, 2026
2 checks passed
@henrypalacios henrypalacios deleted the fix/tag-push-explicit branch April 17, 2026 02:54
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