From ff2ab162d1f22356f9c382f7ef0d1df196a2bae8 Mon Sep 17 00:00:00 2001 From: leodido <120051+leodido@users.noreply.github.com> Date: Mon, 4 May 2026 00:41:02 +0000 Subject: [PATCH] ci: declare GoReleaser config schema version 2 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 --- .goreleaser.yaml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/.goreleaser.yaml b/.goreleaser.yaml index a5919bf..d51ebc7 100644 --- a/.goreleaser.yaml +++ b/.goreleaser.yaml @@ -1,3 +1,7 @@ +# GoReleaser config schema version. v2 is the current major; without +# this header `goreleaser check` warns about an unknown legacy schema. +version: 2 + release: prerelease: auto draft: false