Skip to content

F9.3 — Record the release mechanism

State Closed
Parent E9
Iteration Release 1
Start Date 2026-09-24
Closed Date 2026-09-26
Predecessors ADR-0004

Stories: 3 Closed

Story State Depends on
S9.3.1 — Document current tagging Closed (2026-09-25) —
S9.3.2 — Decide how to handle a partial run Closed (2026-09-26) —
S9.3.3 — Scope CI jobs to changes and dependencies Closed (2026-09-26) —

Outcome: tags are cut by CI, not by hand, and a partial run is prevented by scoping CI to changed packages and their dependents (Release 5, 2026-09-26). The release runbook describes the current mechanism. The risk it addressed was a partial run: a failed package job could leave a dependent tagged against a prerequisite's missing tag.

S9.3.1 — Document current tagging

State: Closed (2026-09-25)

Acceptance: the release runbook states when CI tags, what it builds, what it does not enforce, and the order of steps a release follows.

S9.3.2 — Decide how to handle a partial run

State: Closed (2026-09-26)

Acceptance: the owner chooses how a partial run is prevented, and the runbook states the choice.

The owner chose two changes to the workflow. A failed package job blocks only the packages that depend on it, because each package job waits for its direct internal prerequisites' jobs. And CI runs only the packages a change affects: a package whose source changed, plus every package that depends on it, since each package's tests run against its prerequisites' workspace source.

S9.3.3 — Scope CI jobs to changes and dependencies

State: Closed (2026-09-26)

Acceptance:

  • A first job lists the packages whose files changed and adds every package that depends on one of them, read from the manifests' internal requirements. A workflow_dispatch run selects all seven.
  • Each package job runs only when its package is in that list, and needs: the jobs of its direct internal prerequisites. It still runs when a prerequisite's job was skipped, and does not run when one failed.
  • The sonar and docs jobs still run when some package jobs were skipped.
  • A pull request that changes only rn-forge-sqlalchemy runs only its job; one that changes rn-forge-commons runs all seven, with web before django, fastapi and sqlalchemy.
  • The release runbook describes the scoping and the dependency order.
set -euo pipefail
grep -q '^  changes:' .github/workflows/main.yml

Outcome: the scoping shipped and was observed in GitHub Actions on 2026-09-26.

Acceptance

  • The release runbook documents when CI tags, what it builds and enforces, and the order of steps (S9.3.1).
  • The runbook states the owner's choice for handling a partial run: scope jobs to changes and dependencies, and block only a failed job's dependents (S9.3.2).
  • A first job selects changed packages plus their dependents from the manifests; each package job runs only when selected and waits on its direct prerequisites' jobs; sonar and docs still run when some package jobs were skipped (S9.3.3).