Skip to content

F9.7 — Interim branch pins

State Closed
Parent E9
Iteration Release 1
Start Date 2026-09-26
Closed Date 2026-09-27
Predecessors ADR-0004's interim rule
Source The owner's choice of branch pins over early tags, 2026-09-25, recorded in ADR-0004

Stories: 2 Closed

Story State Depends on
S9.7.1 — Pin internal dependencies to feature/upgrade Closed (2026-09-26) —
S9.7.2 — Restore tag pins for the release Closed (2026-09-27) —

Internal pins named tags that do not exist yet: rn-forge-commons-v0.5.0, rn-forge-cli-v0.1.0 and rn-forge-web-v0.1.0. Inside the workspace the source override hides this; outside it, nothing resolved. Until release-1, internal pins name feature/upgrade instead.

S9.7.1 — Pin internal dependencies to feature/upgrade

State: Closed (2026-09-26)

Acceptance:

  • Every internal rn-forge-* requirement in packages/*/pyproject.toml, extras included, uses @feature/upgrade in place of a tag; uv.lock is refreshed; the workspace validation passes.
  • Outside the workspace, a fresh environment installs rn-forge-fastapi, rn-forge-django and rn-forge-tooling from feature/upgrade.

The manifests were changed and pushed on 2026-09-26. uv lock --check passes, and fresh environments installed and imported rn-forge-fastapi, rn-forge-django and rn-forge-tooling from feature/upgrade.

S9.7.2 — Restore tag pins for the release

State: Closed (2026-09-27)

Acceptance: before S9.6.1, every internal requirement names its release-1 tag again, matching the versions S9.4.1 selected, and the workspace validation passes.

All 17 internal requirements name rn-forge-commons-v0.5.0, rn-forge-web-v0.1.0 or rn-forge-cli-v0.1.0. uv lock --check, the test suite, Ruff and the import contracts pass. The tags do not exist until S9.6.1, so installs outside the workspace fail until then.

Acceptance

set -euo pipefail
absent() { local rc=0; rg -q --hidden --glob '!.git' "$@" </dev/null || rc=$?; [ "$rc" -eq 1 ]; }
absent '@feature/upgrade' -g 'packages/*/pyproject.toml'                  # S9.7.2