Skip to content

docs(release): record publishable-set narrowing + R8 credential path#386

Merged
githubrobbi merged 1 commit into
mainfrom
docs/publish-bootstrap-deviation
Jun 10, 2026
Merged

docs(release): record publishable-set narrowing + R8 credential path#386
githubrobbi merged 1 commit into
mainfrom
docs/publish-bootstrap-deviation

Conversation

@githubrobbi

Copy link
Copy Markdown
Collaborator

What

Two doc updates in docs/architecture/release-automation-plan.md, no behavior change:

  1. New §8.1 deviations-log row ("R8 prep — publishable set narrowed (12 → 2) + credential path", 2026-06-10):

    • cargo metadata --no-deps proves the live publishable set is 2 crates (uffs-time, uffs-text), not the 12/13 cited in historical R0/R3.5/R6 entries (which stay unedited per append-only discipline — this row is the correction of record).
    • Bootstrap publish sequence: both crates are dependency-free leaves — cargo publish -p uffs-time then -p uffs-text (order interchangeable). Dry-runs green, names available.
    • Credential path decision: crates.io Trusted Publishing is configured per-crate in crate settings and requires the crate to already exist (no pending-publisher flow) → first publish must use a maintainer CARGO_REGISTRY_TOKEN; after bootstrap, configure trusted publishers and flip vars.ENABLE_CRATES_IO_PUBLISH (dormant R7 job), then revoke the token.
  2. R7 dashboard row refresh: dormancy gate is the ENABLE_CRATES_IO_PUBLISH repo variable (actionlint rejected the original if: false); clarifies the token-first bootstrap ordering.

Why

Closes the doc-drift loose end found while prepping #240/#241 for the crates.io bootstrap. Companion to #385 (root Cargo.toml comment fix).

Verification

Docs-only; lint-fast + pre-push green.

Adds an R8-prep row to the 8.1 deviations log: cargo metadata proves the

live publishable set is 2 crates (uffs-time, uffs-text), not the 12/13

cited in historical plan/baseline entries; documents the dependency-

ordered bootstrap sequence (both leaves, order interchangeable) and the

credential decision (CARGO_REGISTRY_TOKEN for first publish — trusted

publishing requires the crate to already exist — then OIDC via the

dormant R7 job and token revocation).

Also refreshes the R7 dashboard row: the dormancy gate is the

ENABLE_CRATES_IO_PUBLISH repo variable, not the original if:false.
@githubrobbi githubrobbi enabled auto-merge (squash) June 10, 2026 21:11
@githubrobbi githubrobbi merged commit d496d03 into main Jun 10, 2026
19 checks passed
@githubrobbi githubrobbi deleted the docs/publish-bootstrap-deviation branch June 10, 2026 21:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant