Skip to content

ci: pin goreleaser to 2.15.3#394

Open
muse-sisay wants to merge 1 commit into
masterfrom
ci/pin-goreleaser-2.15.3
Open

ci: pin goreleaser to 2.15.3#394
muse-sisay wants to merge 1 commit into
masterfrom
ci/pin-goreleaser-2.15.3

Conversation

@muse-sisay

Copy link
Copy Markdown
Contributor

GoReleaser 2.16.0 changed goreleaser check to exit non-zero whenever the config uses deprecated properties, even when it is otherwise valid (configuration is valid, but uses deprecated properties). Since our .goreleaser.yml still uses brews and dockers, the GoReleaser Check workflow now fails on every push to master (CI resolves ~> v2 to 2.16.0).

This pins both goreleaser-check.yml and release.yml to 2.15.3, which treats these as warnings and exits 0, restoring a green pipeline.

The config itself is unchanged and still valid. We will migrate the deprecated properties (brewshomebrew_casks, dockersdockers_v2) and unpin the version in an upcoming release.

Same fix as civo/cli#591

GoReleaser 2.16.0 makes 'goreleaser check' exit non-zero when the
config uses deprecated properties (brews, dockers), breaking the
GoReleaser Check workflow on every push to master. Pin both workflows
to 2.15.3, which treats these as warnings, until we migrate to
homebrew_casks and dockers_v2 in an upcoming release.
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