ops-ci-01 bdf9f68175 docs(ci): state the measured push-CI model in ci.yml's when-comment ...

The old comment said push CI is restricted to "protected branches (main)",
which implied next lacked post-merge verification. next is protected and the
default branch since 2026-08-19, and it is not unverified: publish.yml's
verify step runs the complete mandatory set on every push to next, mirroring
this pipeline step-for-step (enforced by verify-release.test.mjs). The
postgres run and push-ci status context it does not re-run duplicate
pre-merge coverage, since PR CI tests the merge ref whose tree equals the
squash commit. Measured 2026-08-19: the 21 most recent push events on next
each ran exactly one pipeline (publish), zero ci. No behavior change.

2026-08-19 17:45:24 -05:00

..

ci-image.yml

fix(ci): image pushes read the registry secrets that exist (#1275) (#1306)

2026-08-18 05:02:23 +00:00

ci.yml

docs(ci): state the measured push-CI model in ci.yml's when-comment

2026-08-19 17:45:24 -05:00

publish.yml

fix(ci): image pushes read the registry secrets that exist (#1275) (#1306)

2026-08-18 05:02:23 +00:00