F19.3 — Internal requirements become ranges
| State | Closed |
| Parent | E19 |
| Iteration | Release 6 |
| Start Date | 2026-10-25 |
| Closed Date | 2026-10-25 |
| Predecessors | F19.1, F19.2, F18.1–F18.4 |
| Source | Owner request, 2026-10-24 |
Stories: 2 Closed
| Story | State | Depends on |
|---|---|---|
S19.3.1 — rn-forge-devops requirements |
Closed | — |
| S19.3.2 — Every internal requirement becomes a range | Closed | S19.3.1 |
Outcome: on 2026-10-25 every requirement from one rn-forge-* package on
another became a name and a range, and rn-forge-devops requirements rejects
one that is not. The range and bump rules are in
ADR-0004; a consumer's usage is in the
consuming guide and the pre-merge check
is in the release runbook.
Design
The release that shipped this moved every dependent to ranges on the Release 6
set, so it is the last release that re-tagged dependents to move a pin. The
check lives in its own rn-forge-devops module, apart from the planner that
left for kiln, and a pykit-owned reusable workflow calls it from CI.
S19.3.1 — rn-forge-devops requirements
State: Closed
Acceptance:
- The check behaves as under Design, its tests pass,
main.ymlcallsinternal-ranges.yml, andci-okneeds it. - It fails on today's manifests, which still use URLs, until S19.3.2 lands.
Merge the two together, or land S19.3.1 with the called job marked
continue-on-error: trueand remove that in S19.3.2.
S19.3.2 — Every internal requirement becomes a range
State: Closed · Depends on: S19.3.1
Acceptance:
- No
packages/*/pyproject.tomlnames a pykit git URL. rn-forge-devops requirementspasses.- The runbook, README, architecture and changelog lines hold.
- After the cut, every dependent installs by name from the index.
Acceptance
set -euo pipefail
absent() { local rc=0; rg -q --hidden --glob '!.git' "$@" </dev/null || rc=$?; [ "$rc" -eq 1 ]; }
(cd packages/rn-forge-devops && uv run pytest -q tests/test_ci.py) # S19.3.1
absent 'git\+https://github.com/rn-forge/pykit@' --glob 'packages/*/pyproject.toml' # S19.3.2
uv run rn-forge-devops requirements # S19.3.1 S19.3.2
uv lock --check && uv run lint-imports && uv run pyright # S19.3.2
uv run --group docs mkdocs build --strict # S19.3.2
# After the cut (S19.3.2): a consumer locks the newest compatible set by name.
tmp=$(mktemp -d); cd "$tmp"
uv init -q --no-workspace demo && cd demo
printf '\n[[tool.uv.index]]\nname = "rn-forge"\nurl = "https://rn-forge.github.io/pykit/simple/"\n' >> pyproject.toml
uv add -q rn-forge-tooling rn-forge-django rn-forge-fastapi rn-forge-sqlalchemy 'rn-forge-data[pandas]'
uv run python -c 'import rn_forge.tooling, rn_forge.django, rn_forge.fastapi, rn_forge.sqlalchemy, rn_forge.data.pandas, rn_forge.commons.generation'
Considered and rejected
- Floors only (
>=0.7.0), no ceiling. A breaking release of a dependency would install under a dependent never tested against it. ~=0.7.0. Before 1.0 it means>=0.7.0,<0.8, which is right. But it changes meaning at 1.0 (~=1.0.0is<1.1), so the explicit pair stays correct across the 1.0 boundary.- Ranges only within a release batch, URLs to anything outside it. It keeps the cascade for every package that was not released in the batch, which is most of them.