Sign release images keyless, with SBOMs and build provenance (K-W6) #131

Merged
jcoffey-dev merged 1 commits from feat/sign-images into main 2026-11-19 23:15:50 +00:00
Owner

Closes #108. The same signing inbuxa-server has (K-S7, server #492/#493), for this repository's one image.

.github/workflows/sign.yml:

  • signs the multi-arch index keyless with cosign, in the registry and on GHCR, and checks both with cosign verify;
  • SPDX SBOMs (syft): one per architecture of the image as shipped, attested against that architecture's digest, and one of the app from package-lock.json at the tagged commit, attested against the index. The image's node_modules are the server's; the browser app's packages are bundled into web/dist, where an image scan can't see them.
  • build provenance, only from the release's own run;
  • attaches the SBOMs to the Gitea release.

ci.yml calls it on a release tag once publish has run (and after the GHCR copy, signed too when it's there). It's in the report, so a signing failure fails the tag's check; the announcement has gone out by then, and the fix is running sign.yml by hand with the tag.

Same pinned cosign v3.1.4 / syft 1.55.0 (sha256-checked) and actions/attest / attest-build-provenance pinned by commit.

Test after merge: run sign.yml by hand on GitHub for inbuxa-v27.1-rc.10 and check with cosign verify and gh attestation verify, as was done for server rc.33.

Closes #108. The same signing inbuxa-server has (K-S7, server #492/#493), for this repository's one image. `.github/workflows/sign.yml`: - signs the multi-arch index keyless with cosign, in the registry and on GHCR, and checks both with `cosign verify`; - SPDX SBOMs (syft): one per architecture of the image as shipped, attested against that architecture's digest, and one of the app from `package-lock.json` at the tagged commit, attested against the index. The image's node_modules are the server's; the browser app's packages are bundled into `web/dist`, where an image scan can't see them. - build provenance, only from the release's own run; - attaches the SBOMs to the Gitea release. `ci.yml` calls it on a release tag once `publish` has run (and after the GHCR copy, signed too when it's there). It's in the report, so a signing failure fails the tag's check; the announcement has gone out by then, and the fix is running `sign.yml` by hand with the tag. Same pinned cosign v3.1.4 / syft 1.55.0 (sha256-checked) and `actions/attest` / `attest-build-provenance` pinned by commit. Test after merge: run `sign.yml` by hand on GitHub for `inbuxa-v27.1-rc.10` and check with `cosign verify` and `gh attestation verify`, as was done for server rc.33.
jcoffey-dev added 1 commit 2026-11-19 23:11:51 +00:00
Sign release images keyless, with SBOMs and build provenance (K-W6)
ci / node (pull_request) Skipped
ci / version (pull_request) Skipped
ci / docker-build (pull_request) Skipped
ci / publish (pull_request) Skipped
github/ci (branch) GitHub Actions
ci / github (pull_request) Successful in 2m22s
ci / announce (pull_request) Skipped
78f49cbb72
sign.yml, as inbuxa-server has (K-S7), for this repository's one image:
signs the index keyless with cosign in the registry and on GHCR and
checks both; attests an SPDX SBOM per architecture, and one of the app
from package-lock.json at the tag, since the browser app's packages are bundled into web/dist, where an image scan can't see them; attests the
build from the release's own run; attaches the SBOMs to the Gitea
release. ci.yml calls it on a release tag once publish has run; it can be
run by hand for a release made before it existed.
jcoffey-dev merged commit ddbccc06f1 into main 2026-11-19 23:15:50 +00:00
jcoffey-dev deleted branch feat/sign-images 2026-11-19 23:15:51 +00:00
Sign in to join this conversation.