chore(ci): run the lock bump daily instead of weekly
Some checks failed
Check / eval (push) Has been cancelled

Move bump.yml's schedule from Mondays to every day (temporarily 17:39
UTC to trigger a run shortly). Sync the ROADMAP cadence note + shipped
log to match.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
2026-07-20 18:37:20 +01:00
parent 757fa873b8
commit 5b95f6444f
2 changed files with 11 additions and 8 deletions

View File

@@ -1840,8 +1840,9 @@ Design/decision records and a running log of shipped work (items marked
builds `system.build.toplevel`, and on green lands on `main` — which nobody
tracks, so a bad bump costs a debug session, not a user outage; `v1` stays
the manual on-hardware gate (it only ever fast-forwards, never force-pushed,
or a user's locked rev can vanish from history). **Cadence weekly**
(release-26.05 doesn't move fast; nightly is just churn), and `nix flake
or a user's locked rev can vanish from history). **Cadence daily**
(2026-07-20; was weekly — release-26.05 doesn't move fast, but daily
shrinks security-patch latency and a no-op bump is cheap), and `nix flake
update` stays *within* the pinned release branches — no surprise major bump
(a 26.11 jump is a deliberate `v2`, hand-edited in flake.nix). Side benefit:
shrinks the security-patch latency the single-input model otherwise imposes
@@ -1849,8 +1850,9 @@ Design/decision records and a running log of shipped work (items marked
already eval/build/VM-tested and one hardware promotion away from `v1` —
worth fast-laning lock-only/security bumps ahead of feature batches.
**Shipped since:** `.gitea/workflows/check.yml` (eval tier on every main
push) and `bump.yml` (Monday 05:17 UTC scheduled lock bump, eval + V1
build gate, auto-lands on green — first landing 8fded63, 2026-07-06).
push) and `bump.yml` (daily 17:39 UTC scheduled lock bump, eval + V1
build gate, auto-lands on green — first landing 8fded63, 2026-07-06;
cadence weekly→daily 2026-07-20).
2026-07-12: both gates moved from one big `nix flake check --no-build`
(~6.0 GB peak RSS — OOM'd the 4 GB VPS, then could never fit the
runner's 2 GB container cap) to `tools/ci-eval.sh`, one output per nix