v30.3-roots.1 · Commit 66: [PATCH 66/68] fix(release): validate notices and reuse proven promotion CI
AGENTS.md
Before: AGENTS.md · After: AGENTS.md
File metadata
index 3f00d5bc6ed49875d2a8f9715ae08fc467924ff8..2189bccaa98d638c15684d529af8bce812033a66 100644
Download original patch · Release notes
Diff rows 1–30 of 30. Line numbers refer to the original before/after files.
+ Added− RemovedUnmarked lines are context.
Scroll the code area horizontally to read long lines. Before is on the left; after is on the right. Unified view fits narrow screens more easily.
AGENTS.md
CHANGED
|
@@ -452,16 +452,21 @@ product patch, and verifies replay onto the matching Core base. Because the
|
|
| 452 |
series contains inherited CRLF files, apply the released mbox with
|
| 453 |
`git am -3 --keep-cr <bitcoin-roots-*.patch>`.
|
| 454 |
|
| 455 |
-
Before assigning a permanent release tag:
|
| 456 |
-
|
| 457 |
-
1. Complete independent source review and merge the reviewed promotion. Verify
|
| 458 |
-
canonical product equality and enumerate repository-only main exceptions.
|
| 459 |
-
2. A manual `Release artifacts` dispatch may rehearse an absent future tag at
|
| 460 |
-
its full canonical commit. It builds all five platforms and their exact
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 461 |
runner dependency notices with read-only permissions; it cannot sign or
|
| 462 |
-
create a release.
|
| 463 |
-
3. Review the source, required CI and rehearsal evidence. Keep the canonical
|
| 464 |
-
tip stable. Re-fetch refs, create one annotated tag explicitly at the reviewed
|
| 465 |
canonical commit, run the release-source validator and push only that tag.
|
| 466 |
4. The tag push builds all five platforms anew, captures installed dependency
|
| 467 |
notices in each runner and generates/replays the portable patch. Only the
|
|
|
|
| 452 |
series contains inherited CRLF files, apply the released mbox with
|
| 453 |
`git am -3 --keep-cr <bitcoin-roots-*.patch>`.
|
| 454 |
|
| 455 |
+
For canonical CI, main promotion and release tagging:
|
| 456 |
+
|
| 457 |
+
1. Complete independent source review and required candidate CI, then integrate
|
| 458 |
+
canonical by fast-forward. Open the main promotion only after that exact
|
| 459 |
+
candidate CI succeeds. The promotion verifies canonical-tip/tree/workflow
|
| 460 |
+
parity and exact successful canonical-target CI before reusing compiled
|
| 461 |
+
test results; classifier/lint and applicable main docs/site checks remain.
|
| 462 |
+
Missing or mismatched promotion proof fails. Explicit ci:* labels request
|
| 463 |
+
fresh coverage. Merge the reviewed promotion with its main exceptions.
|
| 464 |
+
2. Optional manual `Release artifacts` dispatch may rehearse an absent future
|
| 465 |
+
tag at its full canonical commit. It builds all five platforms and their exact
|
| 466 |
runner dependency notices with read-only permissions; it cannot sign or
|
| 467 |
+
create a release. It is not a prerequisite for the normal tag release.
|
| 468 |
+
3. Review the source, required CI and any optional rehearsal evidence. Keep the
|
| 469 |
+
canonical tip stable. Re-fetch refs, create one annotated tag at the reviewed
|
| 470 |
canonical commit, run the release-source validator and push only that tag.
|
| 471 |
4. The tag push builds all five platforms anew, captures installed dependency
|
| 472 |
notices in each runner and generates/replays the portable patch. Only the
|