Repository navigation
Releases
v2.1.0: build provenance
A new optional input, provenance, uploads build provenance bundles from actions/attest-build-provenance (its bundle-path output) to the same release, after the SBOMs (#9). Affectra (affectra/affectra ADR 0024, API 0.1.6 or later) verifies them like SBOM signatures. Its release page then lists each firmware image on the Firmware tab, with the run that built it and the SBOMs that describe it. The IDs come out as attestation-ids, and the job summary gets a provenance table. On an older Affectra the step says the server does not accept build provenance yet. Workflows that don't set provenance behave as before.
v2.0.2: retry once when rate-limited
When Affectra refuses an upload with 429 Too Many Requests (API rate limits, affectra/affectra ADR 0018), the action waits the Retry-After seconds (30 if missing, no wait above 300) and retries once; if it's still refused, it fails with the error's detail and code (#8). Connection errors and 5xx answers are retried as before. Inputs and requests are unchanged.
v2.0.1: error details from problem-details answers
When an upload fails, the action prints the error's English detail and its code, e.g. this organization accepts only SBOMs signed by one of its trusted publishers [sbom.signatureRequired], instead of the raw JSON body that Affectra now sends (affectra/affectra#108). Plain-text answers from older Affectra servers are printed as before (#7). Inputs and requests are unchanged.
v2.0.0: variants
Breaking. Affectra calls the level between a product and its releases a variant now (ADR 0011), and it's optional (#6).
- The input
hardware-revisionis nowvariant, and optional. Without it, the upload goes into the product'sdefaultvariant. - The warning for a newly created variant, the release notice and the job summary leave out
default. - Affectra refuses uploads that still send
hardware_revision(400), so a workflow left on v1 fails instead of uploading into the default variant.
From v1: rename hardware-revision: to variant: and change @v1 to @v2. Your existing releases keep their names. See "From v1" in the README.
v1.2.2: renamed to Affectra
v1.2.1: SBOM attestations documented
Documentation only (#3).
v1.2.0: signed SBOMs
SBOMs can now carry a Sigstore signature, which Exposa verifies on upload and shows as signed when one of your organization's trusted publishers made it (Exposa ADR 0007).
New
sign: true: signs each SBOM keyless with cosign and uploads the signature with it. Needssigstore/cosign-installerandpermissions: id-token: write.- Signature files next to the SBOM: a
<file>.sigstore.jsonis uploaded as that SBOM's signature, and*.sigstore.jsonfiles are never uploaded as SBOMs. - SBOM attestations: save the bundle from
actions/attest-sbomas<file>.sigstore.json. Exposa verifies it and records which files (e.g. firmware images) the SBOM describes. Needs an Exposa version with attestation support; public repositories only for now. - The job summary has a Signature column (
verified,untrusted,unsigned).
Behavior
- A signature by a repository your organization doesn't trust is stored as "signed, untrusted", with a warning.
- The step fails on a signature that doesn't verify (400), when the organization requires signed SBOMs and the upload has none (403), and retries when Exposa can't check signatures right now (503).
Without sign and without .sigstore.json files, uploads work as in v1.1.0.
See the README.