statecraft.
Catalog/rustev

053-signed-release-candidates

Signed release candidates published only as GitHub pre-releases (amends 031)

Lifecycle approvedImplementation completeVerification unknownQualification unknown

A narrow amendment of approved spec 031 (3.9, 3.11, 3.12). It adds a release candidate: an owner-signed annotated tag `vX.Y.Z-rc.N` on a commit of `main`, built and checked by the release workflow exactly as a release is, and published only as a GitHub pre-release of this repository. A candidate never reaches crates.io, the npm registry or the container registry, never consumes spec 031 3.11's first-release authority, and is the identity a downstream consumer such as traveler (`statecrafting/tm`) pins with a Cargo git dependency. An integration rehearsal branch, `release/next`, is where each candidate commit is rehearsed before the owner signs it. Ratified by the owner on 2026-10-25 (A-55).

Read the full pinned specification ↗

Relationships

Claimed units

  • extends
    {
  "nature": "amending",
  "spec": "031-public-api-and-release-family",
  "unit": {
    "kind": "directory",
    "path": "tools/rustev-release/"
  }
}

Source headings

  1. 053: Signed release candidates published only as GitHub pre-releases (amends 031)
  2. 1. Purpose
  3. 2. Territory
  4. 3. Release candidates
  5. 3.1 The integration rehearsal branch
  6. 3.2 The candidate tag
  7. 3.3 The candidate run
  8. 3.4 What a candidate never does
  9. 3.5 Consumption
  10. 4. Out of scope
  11. 5. Observable negative cases
  12. Acceptance
  13. Verification
  14. Implementation record
  15. Decisions at approval

Frozen anchors

No frozen anchors declared.