You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## Problem
When a prerelease and final tag point at one commit, GoReleaser
auto-detects the prerelease tag. Production workflow runs then build
prerelease-named assets and fail before distribution publication.
## Change
Set GORELEASER_CURRENT_TAG from the reusable workflow tag input in
binary, Windows, Public ECR, and Lambda GoReleaser invocations. Add a
workflow test that guards every invocation.
## Security impact
Artifact names, release metadata, and image digest files now derive from
the verified workflow tag even when several tags identify the same
source commit.
## Verification
- make test workflow-validate
## Release recovery
The failed v0.0.42 and v0.5.1 attempts remain unused in dist.
Replacement releases use new patch versions after this shared workflow
patch is published.
Co-authored-by: Paul Querna <paul.querna@conductorone.com>
Co-authored-by: c1-squire-dev[bot] <c1-squire-dev[bot]@users.noreply.github.com>
Copy file name to clipboardExpand all lines: docs/release-workflow.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -136,6 +136,8 @@ checked-out commit matches the tag target before building artifacts or recording
136
136
registry metadata. This prevents a release run from publishing artifacts for one
137
137
commit while labeling them as a different tag.
138
138
139
+
Every GoReleaser invocation receives `GORELEASER_CURRENT_TAG` from the workflow input. This pins archive names, release metadata, and image digest files to the requested tag when multiple tags identify the same commit.
0 commit comments