F20.4 — Release provenance
| State | Closed |
| Parent | E20 |
| Iteration | Release 7 |
| Start Date | 2026-10-28 |
| Closed Date | 2026-10-30 |
| Predecessors | F20.1 |
| Source | Owner request, 2026-10-26 |
Stories: 3 Closed
| Story | State | Depends on |
|---|---|---|
| S20.4.1 — SBOM per package tag | Closed | — |
| S20.4.2 — Attest release artifacts | Closed | — |
| S20.4.3 — Consumer verification guide | Closed | — |
Let a consumer who pins a package tag verify where it came from and what it contains. Each package tag gets a CycloneDX SBOM, and release tags get artifact attestations. This is the largest E20 feature, because it changes the release workflow.
Design
Decided in ADR-0015: the SBOM is cyclonedx-py
CycloneDX JSON, and artifacts carry GitHub and PEP 740 attestations. The release
job is described in the
release runbook and verification in
the verification guide; a source build
from a tag is not covered.
S20.4.1 — SBOM per package tag
State: Closed
Acceptance: each package release uploads a CycloneDX SBOM beside its wheel and sdist on the GitHub Release.
Evidence: rn-forge-commons-v0.8.0 carries rn-forge-commons-0.8.0.cdx.json,
the wheel and the sdist, from
the main run on the merge.
S20.4.2 — Attest release artifacts
State: Closed
Acceptance: release artifacts carry an attestation, and a documented verification command succeeds for a released tag and fails for a modified file.
Evidence: gh attestation verify from the
verification guide exits 0 on the
rn-forge-commons-v0.8.0 wheel and the SBOM, and exits 1 on a copy of the wheel
with a byte appended. PyPI attestations are S21.3.5.
S20.4.3 — Consumer verification guide
State: Closed
Acceptance: a guide shows a consumer how to verify a pinned tag's origin and read its SBOM.
Acceptance
- S20.4.1: the release job attaches the SBOM.
- S20.4.2: the verification command passes on a real release tag.
- S20.4.3: the docs build passes with the guide.