goreleaser: Apparent regression in goreleaser-pro v2.3.0 around docker builds
What happened?
On the v2.3.0 release, our security check github action that uses goreleaser to build a snapshot image for test started failing. It appears that it’s failing because the produced target is linux_amd64_v1 but it’s failing to associate that target with any of the docker image declarations.
I was unable to reproduce this locally with v2.3.0, which is what makes me think that it’s pro-specific.
Downgrading to v2.2.0 fixed the issue, so we have a workaround for the time being.
Let me know if there’s other context that would be helpful.
How can we reproduce this?
Here’s the configuration file that was failing: https://github.com/authzed/zed/blob/16b534dc31a2012e9593616440cb86b2f045b857/.goreleaser.yml
Note that that doesn’t pass check, but modifying it to pass check didn’t fix the issue.
Here’s a link to the github action configuration: https://github.com/authzed/zed/blob/16b534dc31a2012e9593616440cb86b2f045b857/.github/workflows/lint.yaml#L74-L79
Here’s a link to a failing run: https://github.com/authzed/zed/actions/runs/10853416407/job/30121632293
The step that it fails on is the trivy step, but it’s because the build is being skipped in goreleaser:
• docker images
• pipe skipped reason=4 errors occurred:
* partial build, skipping Docker image that does not match target "linux_amd64_v1"
goreleaser version
`:latest` on the github action. Presumably v2.3.0.
GoReleaser Check
- goreleaser check shows no errors
Search
- I did search for other open and closed issues before opening this
Supporter
Code of Conduct
- I agree to follow this project’s Code of Conduct
Additional context
No response
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 15 (10 by maintainers)
Got it. Thanks!