Release 4 — kiln readiness
| Status | shipped |
| Start Date | 2026-10-13 |
| Finish Date | 2026-10-16 |
Make pykit ready for kiln to render
(E16). The workspace CI planner
moves into a new rn-forge-devops package that kiln's generated CI can reach
(F16.1), and pykit passes the shared standard on current lint and type tools,
mdformat and Keep a Changelog (F16.2).
The package boundaries kiln renders are settled too
(E15): the rule for when a
part of commons becomes a package (F15.1), and the rn-forge-data package for
the Excel and pandas helpers (F15.3). The cutover onto kiln (F16.3) and
authentication (E13) are in
Release 7.
Back to releases · Release runbook
Entry criteria
- Release 3 is shipped.
Scope
| Feature | Epic | State |
|---|---|---|
| F15.1 — Package boundary rule | E15 | Closed |
| F15.3 — rn-forge-data package | E15 | Closed |
| F16.1 — The workspace planner ships in rn-forge-devops | E16 | Closed |
| F16.2 — pykit passes the shared standard | E16 | Closed |
Order
- F16.2 first. It rewrites lint sites,
__all__lists, every README and changelog and all Markdown, which are the files the moves touch. It has no predecessor. - F16.1 in parallel. It adds a package and touches
main.ymland the runbooks. kiln's F6.4 waits on thern-forge-devops-v0.1.0tag. - F15.1 in parallel. It is a decision with no code, plus its import contracts.
- F15.3 after F15.1 and F16.2.
Decisions
- ADR-0011, when a part of commons becomes its own package (accepted 2026-10-15, S15.1.1).
- ADR-0012, CI and release logic ships as the
rn-forge-devopspackage, never as workflow logic or copied scripts (accepted 2026-10-15, S16.1.1).
Breaking changes
rn-forge-commons0.6.0 loses itsexcelandpandasextras and the code behind them, which moved to the newrn-forge-data0.1.0.rn-forge-django0.5.0 repoints itstransferandfixturesextras torn-forge-data;transferno longer pullsdjango-import-export[xlsx].rn-forge-fastapi0.3.0 repoints itstransferextra torn-forge-data.
Every internal pin to rn-forge-commons stays at rn-forge-commons-v0.5.0, so
rn-forge-web, rn-forge-cli and rn-forge-tooling are not re-released.
rn-forge-data needs nothing from commons that 0.5.0 lacks. Not breaking: the
new package rn-forge-devops 0.1.0 (F16.1) depends on no other rn-forge
package.
Progress
Shipped 2026-10-16. Every feature in scope is closed: F16.2, F15.1 and F15.3
(2026-10-15), then F16.1 (2026-10-16) once rn-forge-devops-v0.1.0 was
published. ADR-0011 and ADR-0012 are accepted. The
push to main at
merge commit 4dadf2b passed every verify, postgres, smoke and suite job plus
import-boundaries, external-install, docs and the Sonar gate, and
published the five versions below. F16.3 moved to Release 5.
Commits
Commits whose subject names a scope ID, newest first:
Exit criteria
- Every feature on this page's Scope is
Closed: F15.1, F15.3, F16.1 and F16.2. rn-forge-devops-v0.1.0and the other tags in Shipped exist with published GitHub Releases, and the external install job passed for each.- ADR-0011 and ADR-0012 are accepted.
docs/_update_board.sh --checkpasses.- The main CI, including the Sonar gate, passes on the release's version bumps.
Shipped
The five packages below were tagged and published by
run 38918392799;
the other four were already published and skipped. Each package's docs site
serves the new version as latest. uvx runs rn-forge-devops from its tag
outside the workspace (S16.1.3).
| Deliverable | Version | Tag | Commit | Verification |
|---|---|---|---|---|
rn-forge-commons |
0.6.0 |
rn-forge-commons-v0.6.0 |
4dadf2b |
published; external-install and docs passed |
rn-forge-data |
0.1.0 |
rn-forge-data-v0.1.0 |
4dadf2b |
published; external-install and docs passed |
rn-forge-devops |
0.1.0 |
rn-forge-devops-v0.1.0 |
4dadf2b |
published; external-install and docs passed; uvx plan from the tag |
rn-forge-django |
0.5.0 |
rn-forge-django-v0.5.0 |
4dadf2b |
published; external-install and docs passed |
rn-forge-fastapi |
0.3.0 |
rn-forge-fastapi-v0.3.0 |
4dadf2b |
published; external-install and docs passed |