Repository navigation
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.