Repository navigation
ci: publish scanned multi-arch images on every merge to main - #22
Merged
TheGreatAxios merged 1 commit intoOct 31, 2026
Conversation
|
Triage: Pass No changes needed from you. A maintainer will review this pull request. Notes:
Triage will approve, request review, label. |
![corbits-triage[bot]](https://avatars.githubusercontent.com/u/275831056?s=60&v=4){kind=small}
TheGreatAxios
deleted the
cl-11863-publish-scanned-multi-arch-images-on-every-merge-to-main
branch
October 31, 2026 15:30
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.
Closes CL-11863
What changed
New
publish.yml, modelled on corbits-triage's publish job:sidecarandhubtargets for the runner arch, scans both with Trivy (critical and high, fixable findings fail), then builds and pusheslinux/amd64andlinux/arm64toghcr.io/corbitsdev/corbits-builder-{hub,sidecar}as:mainand:<sha>.GPL-2.0-only), BuildKit provenance and an SBOM, and a GitHub build-provenance attestation per digest, verifiable withgh attestation verify.contents: read,packages: write,id-token: write,attestations: write. Actions are pinned to the same shas as triage where they overlap.How it was verified
The workflow parses,
bun run format:checkpasses, anddocker buildx build --checkreports no warnings. It runs for real on the first merge after this one.