lerkolabs/uptop
1
1
Fork 0
Code Issues 5 Pull Requests 1 Actions Packages Projects 1 Releases 1 Wiki Activity

fix(release): pin GoReleaser to triggering tag #135

Merged
lerko merged 1 commits from fix/goreleaser-tag-resolution into main 2026-06-19 21:27:01 +00:00
Conversation 0 Commits 1 Files Changed 1
+1
lerko commented 2026-06-17 21:26:25 +00:00
Owner
Copy Link
Copy Source

Summary

  • Set GORELEASER_CURRENT_TAG to github.ref_name in release-binaries workflow
  • Prevents GoReleaser from picking the wrong tag via git-describe when multiple tags point to the same commit

Context

v0.1.0 release failed because GoReleaser resolved to v0.1.0-rc.5 instead of v0.1.0 — both tags were on commit adf8fed. This caused no Gitea release for v0.1.0, which timed out the GitHub mirror workflow.

## Summary - Set `GORELEASER_CURRENT_TAG` to `github.ref_name` in release-binaries workflow - Prevents GoReleaser from picking the wrong tag via git-describe when multiple tags point to the same commit ## Context v0.1.0 release failed because GoReleaser resolved to `v0.1.0-rc.5` instead of `v0.1.0` — both tags were on commit `adf8fed`. This caused no Gitea release for v0.1.0, which timed out the GitHub mirror workflow.
lerko added 1 commit 2026-06-17 21:26:25 +00:00
fix(release): pin GoReleaser to triggering tag
CI / test (pull_request) Successful in 1m43s
Details
CI / lint (pull_request) Successful in 1m22s
Details
CI / vulncheck (pull_request) Successful in 56s
Details
d50a5159d4 
GORELEASER_CURRENT_TAG prevents GoReleaser from resolving the
wrong tag via git-describe when multiple tags point to the same
commit (e.g. v0.1.0 + v0.1.0-rc.5 on adf8fed).
lerko merged commit d50a5159d4 into main 2026-06-19 21:27:01 +00:00
lerko deleted branch fix/goreleaser-tag-resolution 2026-06-19 21:27:01 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
bug
Something isn't working
 distribution
Packaging, publishing, branding
 feature
New functionality
 github
Forwarded from GitHub
 polish
UX/visual refinement
 refactor
Code quality, no behavior change
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
lerko (Tyler Koenig)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: lerkolabs/uptop#135
Delete Branch "fix/goreleaser-tag-resolution"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?