Fix release pipeline: GoReleaser v2 config and untagged-run guard#5
Merged
Conversation
The manually dispatched release run surfaced two issues. GoReleaser v2.17 warns that the config is version: 0 (fatal in a future release); migrated it — version: 2 header, archives format/builds renamed to formats/ids — and validated with goreleaser check plus a full snapshot build of all six targets. And running the Release workflow directly at an untagged ref died with goreleaser's cryptic "git doesn't contain any tags"; a guard step now fails fast with a pointer to the Tag Release workflow instead. Also bumps checkout/setup-go/goreleaser-action to their current majors to clear the Node 20 deprecation warnings on every run.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The first manual release run failed and surfaced two issues in the pipeline:
main(instead of via Tag Release) fails with GoReleaser'sgit doesn't contain any tags. A guard step now fails fast with an actionable message pointing at the Tag Release workflow.yours is version: 0), but it's slated to become fatal. Migrated:version: 2header,archives.format→formats,archives.builds→ids.Validation:
goreleaser checkpasses on v2.17.0 (the exact version the pinned action resolves), and a fullgoreleaser release --snapshotbuilt all six platform archives locally — it even computed1.1.0-SNAPSHOTas the next version, so the tag math is agreeing with the plan.Also bumps
actions/checkout→ v5,actions/setup-go→ v6, andgoreleaser-action→ v6 across all three workflows to clear the Node 20 deprecation warnings stamped on every run.After this merges, the release path is: Actions → Tag Release →
v1.1.0→ Run.Generated by Claude Code