Skip to content

ci: GitHub Release page and SBOM for every tag - #21

Merged
alexeybe1kin merged 1 commit into
mainfrom
ci/release-pages-sbom
Nov 12, 2026
Merged

alexeybe1kin merged 1 commit into
mainfrom
ci/release-pages-sbom

Conversation

@alexeybe1kin

Copy link
Copy Markdown
Collaborator

Queue Lane C item 4 (Release pages, SBOM, signed images).

  • sbom: true on every image build: BuildKit attaches an SPDX SBOM to the image index. The existing attest-build-provenance step signs (Sigstore, keyless) the index digest, so it covers the SBOM too. No new action and no cosign key.
  • A new release job, after the image jobs and only on a v* tag, with contents: write for that job alone. It creates the GitHub Release page, using the version's ## X.Y.Z CHANGELOG section as the notes. If the release already exists, it is left as it is, so a rerun or a workflow_dispatch from the tag is harmless.
  • One CHANGELOG line under Unreleased, with the verify command.

Test plan

  • The YAML parses. The jobs and needs are correct.
  • The awk extraction gives the right section against the latest tag's CHANGELOG.
  • Not exercised until the next tag: PR CI does not run the publish workflow. On the next release, check that the Release page appears and that gh attestation verify oci://IMAGE@DIGEST --owner Conker-AI passes.

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.
@alexeybe1kin
alexeybe1kin merged commit b243c31 into main Nov 12, 2026
3 checks passed
@alexeybe1kin
alexeybe1kin deleted the ci/release-pages-sbom branch November 12, 2026 19:52
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