Repository navigation
ci: GitHub Release page and SBOM for every tag - #21
Merged
Merged
Conversation
BuildKit SPDX SBOM inside the image index (covered by the signed provenance over the index digest); a release job after the images makes the Release page from the version's CHANGELOG section, skipping one that exists.
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.
Queue Lane C item 4 (Release pages, SBOM, signed images).
sbom: trueon every image build: BuildKit attaches an SPDX SBOM to the image index. The existingattest-build-provenancestep signs (Sigstore, keyless) the index digest, so it covers the SBOM too. No new action and no cosign key.releasejob, after the image jobs and only on av*tag, withcontents: writefor that job alone. It creates the GitHub Release page, using the version's## X.Y.ZCHANGELOG section as the notes. If the release already exists, it is left as it is, so a rerun or aworkflow_dispatchfrom the tag is harmless.Test plan
needsare correct.gh attestation verify oci://IMAGE@DIGEST --owner Conker-AIpasses.