cc-ci

recipe-maintainers/cc-ci

Fork 0

Files

History

autonomic-bot dc74b1efb9

continuous-integration/drone/push Build is passing

Details

docs(recipe-customization): make previous/ a documented last-resort — prefer not to use

The previous/ base-repair mechanism exists and can be used when updating tests
if a previous base won't deploy, but it is explicitly a last resort: reach for
it only after the dynamic base (last-green -> main-tip) fails to come up, since
each previous/ re-introduces the per-version patching treadmill the dynamic
base removed. Most recipes (incl. discourse) need none.

2026-06-17 03:36:31 +00:00

perf

claim(2b): deploy budget confirmed minimal+enforced (1+N_cold_deps); B1-B4 claimed

2026-05-31 05:35:46 +00:00

architecture.md

fix(flake): make Hetzner the canonical cc-ci host target

2026-06-01 13:57:45 +00:00

baseline.md

chore: bootstrap cc-ci loop state

2026-05-26 21:07:31 +01:00

concurrency.md

fix(harness): run-keyed run-scoped state files — CONC-A1 (same-domain runs corrupted shared deploy-count)