lars/giant
1
0
Fork 0
Code Issues 2 Pull Requests 2 Actions Packages Projects Releases Wiki Activity

fix: dereference annotated tag to its commit before the push comparison #96

Merged
lars merged 1 commits from ci/fix-annotated-tag-push-check into master 2026-09-04 08:41:57 +02:00
Conversation 0 Commits 1 Files Changed 1
+1 -1

1 Commits

Author SHA1 Message Date
ci b04e7be146 fix: dereference annotated tag to its commit before the push comparison
CI / Sync project version with tag (hand-pushed tags only) (pull_request) Has been skipped
Details
CI / Publish package to Gitea package registry (pull_request) Has been skipped
Details
CI / Type check (ty) (pull_request) Successful in 35s
Details
CI / Format (ruff format) (pull_request) Successful in 36s
Details
CI / Lint (ruff check) (pull_request) Successful in 39s
Details
CI / Tests (pull_request) Successful in 3m26s
Details
CI / Release (bump, changelog, badges, tag) on merge to master (pull_request) Has been skipped
Details 
release-commit.sh creates release tags with `git tag -a`, so
`git rev-parse "$TAG"` returns the annotated tag object's own SHA, not
the commit it points at. Comparing that directly against
`git rev-parse HEAD` was therefore always false, so the atomic
`git push --atomic origin HEAD:master refs/tags/$TAG` never fired — the
release job has been pushing the branch alone and silently dropping
every release tag (confirmed: v0.3.19 landed on master but was never
pushed as a tag). `^{commit}` dereferences the tag to its target commit
so the comparison actually matches.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NnotyatakKNS4NLjDbfYw1
 2026-09-04 08:36:17 +02:00