rcourtman 7645965afe Derive the rollback target for scheduled release rehearsals ... The weekly release-dry-run schedule failed at 'Resolve rehearsal metadata' because GitHub does not apply workflow_dispatch input defaults to schedule events, so rollback_version arrived empty and resolve_release_promotion.py rejected the run. Scheduled runs now pass --derive-rollback-latest-stable, which fills an empty rollback_version with the latest stable tag preceding the rehearsal version (currently v6.0.4 for 6.0.5-rc.3). Manual dispatches keep the explicit rollback_version requirement; the stale prefilled 5.1.29 default is removed so operators state the target themselves. The deployment-installability contract records the scoped scheduled exception.		2026-07-08 13:52:48 +01:00
..
internal	Add Proxmox filter route regression coverage	2026-07-01 23:20:27 +01:00
v6	Derive the rollback target for scheduled release rehearsals	2026-07-08 13:52:48 +01:00
control_plane.json	Update release control to use main	2026-07-05 15:20:37 +01:00
control_plane.schema.json	Map legacy stable releases in control plane	2026-04-11 13:23:07 +01:00