Skip to content

fix(release): pin the tag goreleaser builds - #1

Merged
sydorovdmytro merged 1 commit into
mainfrom
devops-1335/pin-goreleaser-tag
Aug 19, 2026
Merged

fix(release): pin the tag goreleaser builds#1
sydorovdmytro merged 1 commit into
mainfrom
devops-1335/pin-goreleaser-tag

Conversation

@sydorovdmytro

@sydorovdmytro sydorovdmytro commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

The v0.0.1 release run built, pushed and signed 0.0.1-alpha.2 instead: both tags sit on the same commit and goreleaser resolves the current tag with git describe, which picks arbitrarily between them. The run then failed looking for a digest for ghcr.io/loft-sh/semstat:0.0.1, an image it had never built.

Setting GORELEASER_CURRENT_TAG to the ref the workflow is running on removes the guess.

Part of DEVOPS-1335.

Test plan

  • Reproduced locally with goreleaser 2.17.0 against a local registry: confirmed dockers_v2 records one Docker Image artifact per tag, all sharing the manifest digest, so the digest step resolves once the right tag is used.
  • actionlint and zizmor clean.

Two tags on one commit make git describe ambiguous. Releasing v0.0.1 from
a commit also tagged v0.0.1-alpha.2 built, pushed and signed the alpha,
and the run then failed resolving a digest for an image it never made.
@sydorovdmytro
sydorovdmytro merged commit 3103ef8 into main Aug 19, 2026
6 checks passed
@sydorovdmytro
sydorovdmytro deleted the devops-1335/pin-goreleaser-tag branch August 19, 2026 13:17
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