Skip to content

Release 7 — authentication and PyPI distribution

Status shipped
Start Date 2026-10-25
Finish Date 2026-10-30

pykit gains standards-based authentication and authorization for its web applications (E13): settle and record the design (F13.1), create the rn-forge-auth package and move the existing auth code into it (F13.2), then the features the design produces — the login adapters, the session and HTTP surface for Django and FastAPI, authorization context and resource policy, and the removal of the locally issued JWT flows. The package and the framework adapters ship together. It also sets a security baseline with per-release evidence (E20), and every package is published to PyPI (E21). pykit's cutover onto kiln is Release 8.

Back to releases · Release runbook · Security evidence

Entry criteria

  • Release 6 is shipped.

Scope

Feature Epic State
F13.1 — Auth design E13 Closed
F13.2 — rn-forge-auth package E13 Closed
F13.3 — Core contracts and token profiles E13 Closed
F13.4 — Protocol adapters E13 Closed
F13.5 — Django binding E13 Closed
F13.6 — FastAPI binding E13 Closed
F13.7 — Remove the legacy auth flows E13 Closed
F20.1 — Baseline decision E20 Closed
F20.2 — Dependency risk E20 Closed
F20.3 — Source and secret scanning E20 Closed
F20.4 — Release provenance E20 Closed
F20.5 — Disclosure and posture E20 Closed
F21.1 — PyPI as the index E21 Closed
F21.2 — Package metadata for PyPI E21 Closed
F21.3 — Publish from the release job E21 Closed
F21.4 — Consumers install from PyPI E21 Closed

Order

  1. F13.1 first. It is a decision with no code, and settles the package placement F13.2 follows.
  2. F13.2 after F13.1.
  3. F13.1's remaining stories. S13.1.2 (the ADRs) and S13.1.3 (the library evaluation) are independent; S13.1.4 writes the stories of F13.3 to F13.7 once both close, and sets their Iteration to this release.
  4. F13.3 to F13.7 after F13.2, in order: F13.3 (core contracts, token profiles, stores and the fake IdP), F13.4 (protocol adapters over Authlib's core), then F13.5 (Django) and F13.6 (FastAPI), which may run in parallel, then F13.7 (legacy removal).
  5. F21.1 and F21.2 any time. The owner creates each PyPI project and attaches its trusted publisher before F21.3's first PyPI release, because the workflow's token cannot create a project.
  6. F21.3 in main.yml. S21.3.3 closes when this release's merge publishes to PyPI.
  7. F21.4 in the same merge as F21.3, so the install docs are true when the release ships.

Decisions

  • Owner decision, 2026-10-24: the kiln cutover and authentication move here from Release 6, which ships the kit upgrades kiln builds on.
  • Owner decision, 2026-10-26: all of E13's implementation features (F13.3 to F13.7) ship in this release, with the package.
  • Owner decision, 2026-10-26: E21's F21.1 to F21.4 join this release. Every package takes at least a patch bump so it is published to PyPI with complete metadata, and publishing is built in main.yml before the cutover (E21).
  • Owner decision, 2026-10-27: F13.2 does not wait for the kiln cutover (F16.3).
  • Owner decision, 2026-10-27: pykit drops direct SAML; a SAML IdP federates through a broker (S13.1.5).
  • Owner decision, 2026-10-29: the kiln cutover (F16.3) and F16.6 move to Release 8. This release publishes every package to PyPI first, which kiln's release 1 needs.

Breaking changes

  • New package rn-forge-auth at 0.1.0, with oidc and redis extras (F13.2, F13.3, F13.4).
  • rn-forge-commons loses its auth extra and the code behind it; JwksCache is deleted in favour of PyJWT's PyJWKClient (F13.2).
  • rn-forge-web loses the auth types it holds, rn_forge.web.oidc and its auth extra, and keeps the wire contract (F13.2). It gains the csrf-failed problem type (F13.3). This follows E13's package placement.
  • rn-forge-auth's Principal and Requirement change before its first release: permission clauses replace role clauses, and bearer principals carry effective permissions limited by scopes (F13.3).
  • rn-forge-django and rn-forge-fastapi repoint their oidc extras to rn-forge-auth (F13.2). Their bearer authenticators reject a token whose (issuer, subject) has no linked account (F13.5, F13.6).
  • rn-forge-django's bearer authentication classes require an AccountResolver and an AuthorizationContextProvider; it gains a redis extra on rn-forge-auth[redis], and mounting the auth surface requires RN_FORGE_DJANGO["AUTH"]["PROBLEM_TYPE_BASE"] (F13.5).
  • rn-forge-fastapi's bearer_auth() requires an AccountResolver and an AuthorizationContextProvider; rn_forge.fastapi.auth becomes a package; it gains a redis extra on rn-forge-auth[redis], and mounting the auth router requires a problem type_base (F13.6).
  • rn-forge-django loses its jwt extra and simplejwt, the locally issued JWT flows, BaseCredentials, LoginPayload, the auth.basic and auth.saml views, SampleSAMLLoginAPIView and the authorization mixins, and its saml extra and python3-saml: a SAML IdP connects through a broker (F13.7).

Progress

Shipped 2026-10-30. Every feature in scope is closed.

  • E13: the design is settled, and ADR-0006 is revised with ADR-0013 and ADR-0014 accepted. rn-forge-auth holds the core contracts and the login adapters. rn-forge-django and rn-forge-fastapi serve the auth surface and pass the shared security-control cases in rn_forge.auth.conformance. The locally issued JWT flows are removed.
  • E20: the dependency audit, licence inventory, source and secret scans, push protection, SBOMs, attestations and SECURITY.md are in place, and the evidence records each control's result.
  • E21: every package is on PyPI, published from main.yml by trusted publishing. Every project is in the rn-forge PyPI organization.

The first run on the merge published rn-forge-commons 0.8.0 and then failed on rn-forge-devops, because the workflow's token cannot create a PyPI project. The owner created the projects, and S21.3.5 added PEP 740 attestations, signed one file at a time with retries. The push to main at a038a0d passed all 48 jobs, including release, external-install, docs, Sonar, umbrella-release and ci-ok, and published the ten versions below.

The version cut (S21.3.4) took rn-forge-commons, rn-forge-web, rn-forge-django and rn-forge-fastapi, which carry breaking changes, to 0.8.0, 0.3.0, 0.6.0 and 0.4.0, and every internal range on them admits exactly that minor. S21.3.5 then bumped rn-forge-commons to 0.8.1.

Commits

Commits whose subject names a scope ID, newest first:

git log --format='%h %ad %s' --date=short -E --grep='F13\.|S13\.|F20\.|S20\.|F21\.|S21\.'

Exit criteria

  • Every feature on this page's Scope is Closed, including F13.1 to F13.7, F20.1 to F20.5 and F21.1 to F21.4.
  • E13's proposed decisions are recorded as S13.1.2 describes: ADR-0006 revised and two new ADRs accepted.
  • docs/_update_board.sh --check passes.
  • The main CI, including the Sonar gate, passes on the release's version bumps.

Shipped

The ten packages below were tagged and published to PyPI by run 41151600463, with a GitHub release for each. Each release has its changelog section as notes, is not "Latest", and carries only the wheel, the sdist and the .cdx.json SBOM. Each package's docs site serves the new major.minor as latest, and each project belongs to the rn-forge PyPI organization.

All ten were installed together by name from PyPI into a clean virtual environment, and rn_forge.commons, rn_forge.devops, rn_forge.cli, rn_forge.data, rn_forge.web, rn_forge.auth, rn_forge.sqlalchemy, rn_forge.tooling, rn_forge.django and rn_forge.fastapi each imported. PyPI's integrity API returns provenance for all ten wheels. For rn-forge-commons 0.8.1 it names the GitHub repository rn-forge/pykit, workflow main.yml and environment pypi, and gh attestation verify -R rn-forge/pykit passes on its wheel. The security evidence holds the rest.

Deliverable Version Tag Commit Verification
rn-forge-commons 0.8.1 rn-forge-commons-v0.8.1 a038a0d published to PyPI; GitHub release; external-install and docs passed; wheel provenance
rn-forge-devops 0.3.1 rn-forge-devops-v0.3.1 a038a0d published to PyPI; GitHub release; external-install and docs passed; wheel provenance
rn-forge-cli 0.1.2 rn-forge-cli-v0.1.2 a038a0d published to PyPI; GitHub release; external-install and docs passed; wheel provenance
rn-forge-data 0.1.2 rn-forge-data-v0.1.2 a038a0d published to PyPI; GitHub release; external-install and docs passed; wheel provenance
rn-forge-web 0.3.0 rn-forge-web-v0.3.0 a038a0d published to PyPI; GitHub release; external-install and docs passed; wheel provenance
rn-forge-auth 0.1.0 rn-forge-auth-v0.1.0 a038a0d published to PyPI; GitHub release; external-install and docs passed; wheel provenance
rn-forge-sqlalchemy 0.2.2 rn-forge-sqlalchemy-v0.2.2 a038a0d published to PyPI; GitHub release; external-install and docs passed; wheel provenance
rn-forge-tooling 0.3.1 rn-forge-tooling-v0.3.1 a038a0d published to PyPI; GitHub release; external-install and docs passed; wheel provenance
rn-forge-django 0.6.0 rn-forge-django-v0.6.0 a038a0d published to PyPI; GitHub release; external-install and docs passed; wheel provenance
rn-forge-fastapi 0.4.0 rn-forge-fastapi-v0.4.0 a038a0d published to PyPI; GitHub release; external-install and docs passed; wheel provenance