mosaicstack/stack
6
0
Fork 1
Code Issues 298 Pull Requests 18 Actions Packages Projects Releases 15 Wiki Activity
878 Commits 164 Branches 17 Tags
09b7c369c5c247ea81f29589eddbc6583576bbe2
Commit Graph
5 Commits
This Branch
This Branch
All Branches
Author SHA1 Message Date
ops-ci-01 09b7c369c5 Merge remote-tracking branch 'origin/next' into ci/push-ci-comment-model
ci/woodpecker/pr/ci Pipeline was successful
Details
2026-08-19 19:14:40 -05:00
ops-ci-01 ce633b4d50 docs(ci): correct the merge-ref claim; PR CI tests the head tree 
My own comment asserted 'PR CI tests the merge ref, whose tree equals the
landed squash commit' - never measured. Pipeline API refs show pull_request
runs execute refs/pull/N/head (2542, 2545): the head tree, not a merge ref.
If next advances between run and merge, the landed tree differs from the
tested one; that residual is what publish verify re-covers post-merge (full
verify:release on the push, PGlite path). Same evidence discipline this PR
exists to enforce; the claim is corrected to what was measured.
 2026-08-19 19:14:40 -05:00
ops-ci-01 cb9a0d1642 ci: pin ci-base to immutable lock-9cb7ffcd8828 (Closes #1328) (#1329)
ci/woodpecker/push/publish Pipeline was successful
Details 
Co-authored-by: ops-ci-01 <[email protected]>
 2026-08-19 23:42:05 +00:00
ops-ci-01 781a1fddc5 docs(ci): soften protection parenthetical to the measurable claim
ci/woodpecker/pr/ci Pipeline failed
Details 
rev-code-01 review id 215: the branch-protection API is admin-gated for seat
tokens, so 'required status check' cannot be evidenced inline; the comment
states only what carries its own evidence. Protection and default-branch
status are API-readable and stay.
 2026-08-19 18:41:48 -05:00
ops-ci-01 bdf9f68175 docs(ci): state the measured push-CI model in ci.yml's when-comment
ci/woodpecker/pr/ci Pipeline was successful
Details 
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