Repository navigation
Install syft in release workflow - #6
Merged
Merged
Conversation
The .goreleaser.yml sboms block requires syft, but the fork's release workflow never installed it, so releases failed at the cataloging step.
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
sboms:block in.goreleaser.ymlrequiressyfton PATH. Upstream added it alongside a "Setup Syft" step in the release workflow, but this fork'srelease.ymllacks that step, so the v1.27.0 release built for ~25 minutes and then failed:Adds
anchore/sbom-action/download-syft, SHA-pinned for zizmor.Note:
v1.27.0is already tagged, so re-running the failed workflow would use the workflow file from the tagged commit, not this fix — the tag needs to move or a new tag be cut.https://claude.ai/code/session_01EX9isbBaZ2GJnBQgn5QirG