F22.13 — Small release utilities with one metadata path
| State | Closed |
| Parent | E22 |
| Iteration | Release 9 |
| Start Date | 2026-11-14 |
| Closed Date | 2026-11-16 |
| Predecessors | F22.3 |
Stories: 2 Closed
| Story | State | Depends on |
|---|---|---|
| S22.13.1 — Pin requirement-check behavior | Closed (2026-11-14) | — |
| S22.13.2 — Simplify only demonstrated duplication | Closed (2026-11-16) | — |
Keep the release helper small, with a clear metadata parser and focused contract coverage.
Context
The package is four modules and 268 lines after CI planning moved away.
requirements.py parses member dependency declarations; current tests cover a
narrow path compared with versions, extras, URLs and groups. This is primarily a
coverage/readability opportunity, not evidence for a replacement graph or a new
release framework.
S22.13.1 — Pin requirement-check behavior
State: Closed (2026-11-14)
Build tiny temporary workspaces that exercise the requirement forms the checker supports. Specify handling of missing members, exclusions, malformed requirements and unresolved direct references.
Acceptance:
- Ranges, canonicalized names, extras, direct URLs, optional dependencies and dependency groups are either checked correctly or explicitly outside the documented contract.
- CLI exit codes and diagnostic paths distinguish invalid requirements from incompatible internal floors.
- Release-note tests cover package changelog selection, missing sections and stable output.
requirementsexits 0 for no problems, 1 for incompatible requirements and 2 for invalid input. The contract, and the forms it checks or skips, are in the devops subcommands reference.notes.pyselects release pages, so its tests pin page selection.
Outcome: invalid input now raises InvalidManifest, giving exit 2 and a
<manifest path>: <reason> line in place of a traceback.
S22.13.2 — Simplify only demonstrated duplication
State: Closed (2026-11-16)
Use one manifest-to-requirements path within devops and remove obsolete planner prose/imports if found. Compare repeated reads on a synthetic workspace before adding caches.
Acceptance:
- The package remains independent of runtime packages, and no duplicate CI planner is restored.
- Supported CLI commands and generated note text remain stable under focused tests.
- No dependency addition, broad module split or runtime performance claim is required to close this feature.
Settled contract: devops has one manifest-to-requirements path and no obsolete planner code; no cache, because every file is read a constant number of times (one per member manifest, two for the shipped release page).
Outcome: guards pin that plan, smoke and releasable stay removed and
that each member manifest is read once; 500 members check in about 0.11 s.
Acceptance
- S22.13.1: Ranges, canonicalized names, extras, direct URLs, optional dependencies and dependency groups are either checked correctly or explicitly outside the documented contract.
- S22.13.2: The package remains independent of runtime packages, and no duplicate CI planner is restored.