You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit b5db421
Browse filesBrowse the repository at this point in the historyBrowse files
ci(release): refuse ambiguous PRs, harden API reads, require full contexts, fix proof cut-over
Round 2 of the release guard.
Doc deletion, named as the doc-revert gate asks (introducing commit 3cca5e9):
the round-1 line "A release is refused unless the released tree's merged-PR
head carries pineforge/verify and pineforge/parity success, read through the
statuses API (fail closed); main commits carry no statuses." is deleted and
replaced by the "Release guard phases" section: phase 1 keeps the merged-PR-head
transition path (one tree-matching PR, several refuse), phase 2 requires the
main-proof receipt for the exact main sha at and after the fixed cut-over and
never falls back to a PR head.
as an existing hosted exception, while `macos-universal` retains
1063
1063
`macos-latest`. The workflow remains `workflow_dispatch` only.
1064
-
A release is refused unless the released tree's merged-PR head carries `pineforge/verify` and `pineforge/parity` success, read through the statuses API (fail closed); main commits carry no statuses.
1065
1064
1066
1065
The GCP fleet also routes baseline `promote` in `promote-baseline.yml`
1067
1066
to `["self-hosted","pf-gcp-main"]`, preserving L6's 15:40 addendum's
@@ -1252,3 +1251,28 @@ split. Cancelled/failed jobs did skip the old compiler post-save, which reduced
1252
1251
cache freshness; the new save ordering addresses that independently. The
1253
1252
historical ASan startup assertion remains a separate diagnosis, and splitting
1254
1253
jobs does not establish a runtime fix or dismiss a sanitizer failure.
1254
+
1255
+
### Release guard phases
1256
+
1257
+
The release guard requires exactly `pineforge/verify` and `pineforge/parity`
1258
+
to be `success`; lite variants never satisfy either requirement. Phase 1 is
1259
+
the **transitional** merged-PR-head path for main commits that predate the
1260
+
main watcher. It requires exactly one associated merged PR whose head tree
1261
+
matches the released tree, then reads that head's full contexts through the
1262
+
statuses API. Zero matches refuse; multiple matches refuse and name every
1263
+
matching PR, with no preference for the newest.
1264
+
1265
+
Phase 2 is **not live yet**: `MAIN_PROOF_WATCHER_FIRST_SHA` in
1266
+
`scripts/release_gate.py` is `None`. When C2 main-watch (#176) supplies the
1267
+
receipt reader, the cut-over is the watcher's **first recorded main sha**,
1268
+
fixed in that constant by a reviewed PR. The release job cannot configure it
1269
+
through an environment variable or workflow input. At that sha and every
1270
+
descendant, the guard requires a main-proof receipt for the **exact main
1271
+
sha** with both full contexts green and does not consult PR heads. Missing,
1272
+
unreadable or non-green receipts refuse, with no transitional fallback.
1273
+
Commits preceding the cut-over retain phase 1; unknown ancestry refuses.
1274
+
The reader seam defines normalized context states, not a receipt storage format.
1275
+
1276
+
Every API call is a read using the release job's own App token. Rate limits
1277
+
and upstream 5xx responses refuse immediately, naming the failure, without
1278
+
sleeping or retrying; empty or unparseable evidence also refuses.
0 commit comments