Skip to content
Bitcoin Roots

v30.3-roots.1 · Commit 62: [PATCH 62/68] fix(release): create drafts from reviewed immutable assets

AGENTS.md

Before: AGENTS.md · After: AGENTS.md

File metadata
index a593ae772cc2b58b690cc1a406bce164d8abca91..61d32d8ed5c180fd902c58c9a100fb234e51ed6a 100644

Download original patch · Release notes

Diff rows 1–19 of 19. Line numbers refer to the original before/after files.

+ Added− RemovedUnmarked lines are context.

Scroll the code area horizontally to read long lines. The two line-number columns refer to before and after.

AGENTS.md CHANGED
@@ -458,11 +458,16 @@ Before assigning a permanent release tag:
458
458
  2. Dispatch `Release artifacts` from `main` with the future Roots tag and the
459
459
  full 40-hex `origin/roots/<core-version>` commit.
460
460
  3. Require all five platform builds and independently inspect the packages and
461
- patch. Manual rehearsal must create neither a remote tag nor a release.
461
+ patch. Assemble and review platform-specific notices and the final asset
462
+ packet using `ci/release/README.md` before tagging. Manual rehearsal must
463
+ create neither a remote tag nor a release.
462
464
  4. Re-fetch refs, create one annotated tag at the unchanged canonical tip, run
463
465
  the release-source validator, and push only that tag. Never move it.
464
- 5. Verify the tag-triggered draft's packages, patch, `SHA512SUMS`, optional
465
- signature, tag target, and source tree before publishing the unchanged draft.
466
+ 5. Permanent tags do not start builds or create a draft. Use
467
+ `ci/release/create-draft.py` with the approved commit, asset manifest and notes
468
+ digests to validate the permanent remote tag and create a new draft. Verify
469
+ downloaded draft packages, patch, checksums, notes and actual signing status
470
+ before publishing the unchanged draft under separate authority.
466
471
  6. Repeat tag, asset, checksum, and signature-if-present verification through an
467
472
  unauthenticated client after publication.
468
473