PerishLab/plumb
1
0
Fork 0
Code Issues 11 Pull requests 22 Projects Releases Packages 1 Wiki Activity Actions

Advance the pointer, and rehearse only what can be rehearsed #316

Merged
PerishFire merged 1 commit from land/task/advance-the-pointer into main 2026-08-18 09:35:07 +00:00
Conversation 0 Commits 1 Files changed 12 +80 -23
PerishFire commented 2026-08-18 09:32:11 +00:00
Owner
Copy link

Advance the pointer, and rehearse only what can be rehearsed

Stable v0.26.0 published its binaries and its seal, shifted its managers, and
left the consensus pointer at v0.25.0. Shifting the managers and advancing the
pointer are two operations — the skeleton says so in as many words — and the
rendered lane ran only the first, so every smoke installed the release that was
still canonical and reported the mismatch it was there to catch. The lane now
runs both and reads the activated surface back, as the shared workflow does.

The Cargo rehearsal met the coupling this release created. An attachment holds
one unit whose packages pin each other exactly, so the second package cannot be
built from its packaged form until the first is published — cargo package
verifies by building, and the version it needs does not exist yet. That is issue
#137, and under the old model it was hidden by the pins that held siblings back
to versions already on the registry.

A rehearsal now says which packages it cannot rehearse and why, and the ordered
publish is what proves them. Dev-dependencies do not couple, because verification
does not build them.

Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com

Advance the pointer, and rehearse only what can be rehearsed Stable v0.26.0 published its binaries and its seal, shifted its managers, and left the consensus pointer at v0.25.0. Shifting the managers and advancing the pointer are two operations — the skeleton says so in as many words — and the rendered lane ran only the first, so every smoke installed the release that was still canonical and reported the mismatch it was there to catch. The lane now runs both and reads the activated surface back, as the shared workflow does. The Cargo rehearsal met the coupling this release created. An attachment holds one unit whose packages pin each other exactly, so the second package cannot be built from its packaged form until the first is published — `cargo package` verifies by building, and the version it needs does not exist yet. That is issue #137, and under the old model it was hidden by the pins that held siblings back to versions already on the registry. A rehearsal now says which packages it cannot rehearse and why, and the ordered publish is what proves them. Dev-dependencies do not couple, because verification does not build them. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Advance the pointer, and rehearse only what can be rehearsed
All checks were successful
guard / guard (pull_request) Successful in 2m45s
Details
guard / guard (push) Successful in 2m46s
Details
dd42b90303 
Advance the pointer, and rehearse only what can be rehearsed

Stable v0.26.0 published its binaries and its seal, shifted its managers, and
left the consensus pointer at v0.25.0. Shifting the managers and advancing the
pointer are two operations — the skeleton says so in as many words — and the
rendered lane ran only the first, so every smoke installed the release that was
still canonical and reported the mismatch it was there to catch. The lane now
runs both and reads the activated surface back, as the shared workflow does.

The Cargo rehearsal met the coupling this release created. An attachment holds
one unit whose packages pin each other exactly, so the second package cannot be
built from its packaged form until the first is published — `cargo package`
verifies by building, and the version it needs does not exist yet. That is issue
#137, and under the old model it was hidden by the pins that held siblings back
to versions already on the registry.

A rehearsal now says which packages it cannot rehearse and why, and the ordered
publish is what proves them. Dev-dependencies do not couple, because verification
does not build them.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Land-Source: task/advance-the-pointer@971a8b39a9
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
PerishLab/plumb!316
No description provided.