fix(ci): install syft in release.yml (v0.3.1 release recovery)#121
Merged
Conversation
The v0.3.1 release run failed: goreleaser's `sboms:` step shells out to syft,
but release.yml installed only cosign — `exec: "syft": not found`. Builds,
archives, and checksums all succeeded; SBOM cataloging aborted the release
before artifacts/signature attached.
- Install syft via anchore/sbom-action/download-syft (pin reused from
security.yml) before the goreleaser step.
- Add workflow_dispatch(tag) + checkout ref=${{ inputs.tag || github.ref }} so
the fixed workflow can re-run against an already-pushed (immutable) tag;
goreleaser `release: mode: append` attaches artifacts to the existing release
without re-cutting the tag.
actionlint clean. After merge, dispatch with tag=v0.3.1 to recover its signed
artifacts.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LDQVJrixs2nJoea67a8pEG
|
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
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.



Problem
The v0.3.1 release pipeline (first live run of #116's goreleaser+cosign workflow) failed:
exec: "syft": executable file not found in $PATH. GoReleaser built all 4 binaries + archives + checksums, then thesboms:step (which shells out to syft) aborted — release.yml installs cosign but never installed syft. The tag, GH release notes, andgo install @v0.3.1are intact; only the signed binaries didn't attach.Fix
anchore/sbom-action/download-syftbefore the goreleaser step (pin reused fromsecurity.yml).workflow_dispatch(tag)+checkout ref=${{ inputs.tag || github.ref }}so this fixed workflow can be re-run against the already-pushed, immutable v0.3.1 tag — goreleaserrelease: mode: appendattaches artifacts to the existing release without re-cutting the tag (the proxy treats tags as immutable, so re-pushing is off the table).Recovery plan
After merge:
gh workflow run "Release (artifacts + signing)" --ref main -f tag=v0.3.1→ signed binaries + checksums + SBOMs append to the existing v0.3.1 release.actionlint clean. Future tagged releases pick up the fix automatically on tag push.
🤖 Generated with Claude Code