ci: declare GoReleaser config schema version 2#52
Merged
Conversation
Without this top-level 'version: 2' header, 'goreleaser check' on
v2.x emits the deprecation warning:
only version: 2 configuration files are supported, yours is
version: 0, please update your configuration
The release pipeline still works (release.yaml pins goreleaser-action
to v2.14.0 via 'with: version: v2.14.0'), but the warning is noise
and a future major bump may turn it into a hard error. 'goreleaser
init' on v2.x produces this header by default.
Verified locally:
- 'goreleaser check' now passes silently (warning gone)
- 'goreleaser release --snapshot --skip=publish,sign --clean'
still builds both linux_amd64 and linux_arm64 tarballs and
the checksums file with no behavior change
Co-authored-by: Ona <no-reply@ona.com>
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.
Why
goreleaser checkon v2.x emits this deprecation warning when the config lacks a top-levelversionfield:The release pipeline still works today because
.github/workflows/release.yamlpinsgoreleaser-actiontov2.14.0viawith: { version: v2.14.0 }, and v2.14.0 still accepts v0 (legacy) configs with a warning. But:goreleaser initon v2.x produces this header by default — our config is just missing what new configs ship with.This is the followup mentioned as out-of-scope in #51.
What
One-line addition:
version: 2at the top of.goreleaser.yaml, with a brief comment explaining what it is.Verification
goreleaser checkgoreleaser release --snapshot --skip=publish,sign --cleanNo functional change to the release pipeline or the artifacts produced.