F21.3 — Publish from the release job
| State | Closed |
| Parent | E21 |
| Iteration | Release 7 |
| Start Date | 2026-10-28 |
| Closed Date | 2026-10-30 |
| Predecessors | F21.1, F21.2 |
| Source | Owner request, 2026-10-26 |
Stories: 5 Closed
| Story | State | Depends on |
|---|---|---|
S21.3.1 — notes and umbrella commands |
Closed | — |
S21.3.2 — PyPI upload, TestPyPI dry run and release notes in main.yml |
Closed | S21.3.1, S21.1.2 |
| S21.3.3 — First PyPI release and the umbrella | Closed | S21.3.2, S21.3.4, S21.3.5 |
| S21.3.4 — Release 7 version cut | Closed | S21.3.2 |
| S21.3.5 — PEP 740 attestations on PyPI | Closed | S21.3.2 |
Outcome: from the Release 7 merge (2026-10-29), each released package is
uploaded to PyPI by trusted publishing with a PEP 740 attestation, a manual run
can upload to TestPyPI, and a shipped release page produces the umbrella
release-<n> release. The workflow behaviour is described in the
release runbook.
Design
rn-forge-devops: two commands
Per ADR-0012 the release logic lives in the package,
not the workflow. rn-forge-devops notes prints a changelog section and
rn-forge-devops umbrella writes the body of the newest shipped release page;
neither is a planner command, so both stayed in pykit after
S16.3.4.
main.yml
The release job builds, runs twine check --strict, uploads to PyPI before
creating the GitHub release, so a published release implies the version is on
PyPI; the release runbook describes
the job, the TestPyPI dry run and the umbrella workflow.
Registering the publishers
The workflow's token cannot create a PyPI project: after rn-forge-commons was
created through a pending publisher, uploading rn-forge-devops failed with
400 Non-user identities cannot create new projects. The owner therefore
creates each project from the rn-forge organization's page and attaches its
trusted publisher before the first upload; the steps and limits are in the
release runbook. The
rn-forge-devops, rn-forge-cli, rn-forge-data and rn-forge-web projects
were created earlier by <version>.dev0 placeholder uploads, which the owner
deletes after the real versions are published.
S21.3.1 — notes and umbrella commands
State: Closed
Acceptance: the module, CLI, contracts and tests are as under Design, and
rn-forge-devops' tests, lint-imports and pyright pass.
S21.3.2 — PyPI upload, TestPyPI dry run and release notes in main.yml
State: Closed · Depends on: S21.3.1, S21.1.2
Acceptance:
- A pull request run builds and runs
twine checkfor every selected package and uploads nothing. - A manual run with
testpypifrom the release branch, after the projects exist as Registering the publishers describes, uploads every package to test.pypi.org. - One more rerun uploads nothing and succeeds.
- A TestPyPI file page shows a provenance attestation. (Moved to S21.3.5: the packages were uploaded from a local build to attach the publishers, so the files carry none, and the rerun in CI skipped them as already on TestPyPI.)
zizmorandactionlint, wherever the repository runs them, pass on the changed workflows.
S21.3.3 — First PyPI release and the umbrella
State: Closed · Depends on: S21.3.2, S21.3.4, S21.3.5
The story closed after Release 7 merged to main and its ship commit was
pushed. Before the merge that published, the owner created every pypi.org
project and attached its trusted publisher, as
Registering the publishers describes, with
environment pypi. That merge's push publishes the real versions, and the ship
commit follows. A rerun skips what PyPI and GitHub already have.
Acceptance:
- Every package's Release 7 version is on pypi.org.
- A pypi.org file page of a version released after S21.3.5 shows a provenance attestation, and PyPI's integrity API returns it for that file.
external-installpassed from PyPI.- Each per-package release has its changelog section as notes and is not "Latest".
release-7exists and is "Latest".- The placeholder releases are deleted.
- Every pypi.org project has been added to the
rn-forgeorganization (the owner, from the organization's Projects page).
S21.3.4 — Release 7 version cut
State: Closed · Depends on: S21.3.2
Acceptance:
- Every package carries its Release 7 version:
rn-forge-commons0.8.0,rn-forge-web0.3.0,rn-forge-django0.6.0 andrn-forge-fastapi0.4.0, whose breaking changes take a minor bump, and the F21.2 patch bump for the rest. - Dependents' internal ranges admit exactly the new minors, floor and ceiling.
- Each changelog's
[Unreleased]entries sit under a heading for that version, dated 2026-10-29. rn-forge-devops requirements,docs/_update_board.sh --checkand the workspace validation pass.
S21.3.5 then bumps rn-forge-commons to 0.8.1, which the dependents' ranges
(>=0.8.0,<0.9) already admit.
S21.3.5 — PEP 740 attestations on PyPI
State: Closed · Depends on: S21.3.2
rn-forge-commons 0.8.0 reached PyPI without attestations: uv publish uploads
the *.publish.attestation files it finds beside the distributions and never
generates them, and actions/attest-build-provenance writes GitHub attestations
only. rn-forge-commons is bumped to 0.8.1 so a version with attestations
exists.
Acceptance:
- The release job signs a publish attestation for each built file with
pypi-attestations sign, retrying each file on its own. uv publishuploads those files with the distributions.- The GitHub release assets are the wheel, the sdist and the SBOM, without the attestation files.
rn-forge-commonsis at 0.8.1 with a dated changelog section, and 0.8.1 is the first version with PyPI attestations.
Signing each file with retries succeeded on the first real run (run 41151600463).
Acceptance
set -euo pipefail
cd packages/rn-forge-devops && uv run pytest -q tests/test_notes.py tests/test_cli.py && cd ../.. # S21.3.1
uv run lint-imports && uv run pyright packages/rn-forge-devops # S21.3.1
# After the TestPyPI dry run (S21.3.2):
for d in packages/*/; do
name=$(basename "$d"); v=$(uv version --package "$name" --short)
curl -fsS -o /dev/null "https://test.pypi.org/pypi/$name/$v/json"
done
# After Release 7 ships (S21.3.3, S21.3.5):
for d in packages/*/; do
name=$(basename "$d"); v=$(uv version --package "$name" --short)
curl -fsS -o /dev/null "https://pypi.org/pypi/$name/$v/json"
gh release view "$name-v$v" --json body,isLatest --jq 'select(.isLatest | not) | .body' | grep -q '^### '
done
v=$(uv version --package rn-forge-commons --short)
curl -fsS -o /dev/null "https://pypi.org/integrity/rn-forge-commons/$v/rn_forge_commons-$v-py3-none-any.whl/provenance" # S21.3.5
tmp=$(mktemp -d); (cd "$tmp" && uv init -q --no-workspace demo && cd demo \
&& uv add -q "rn-forge-commons==$v" && uv run python -c 'import rn_forge.commons')
[ "$(gh api repos/rn-forge/pykit/releases/latest --jq .tag_name)" = release-7 ]