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

Stop adding a v the version already carries #361

Open
PerishFire wants to merge 1 commit from task/the-version-already-carries-its-v into main
pull from: task/the-version-already-carries-its-v
merge into: PerishLab:main
Conversation 0 Commits 1 Files changed 2 +3 -3
PerishFire commented 2026-08-19 03:46:44 +00:00
Owner
Copy link

The generator built the URL of its own published seal as v{running}, and plumb::version! already yields v0.27.0-beta.6:

plumb release: cannot read back .../v1/releases/beta/vv0.27.0-beta.6/seal.json: 404

Every prerelease binary looked for a doubled prefix and refused the release it was running.

It appeared the first time a release was generated by an exact point — the first time this path had ever executed, since the bootstrap it belongs to landed one commit earlier and could not run until a channel pointer existed.

The run that found it also proves the rest works:

installed plumb v0.27.0-beta.6 to /tmp/plumb-v0.27.0-beta.6/bin

The lane read the pointer and installed the newest published exact rather than canonical stable, which is the whole of what the bootstrap is for.

The generator built the URL of its own published seal as `v{running}`, and `plumb::version!` already yields `v0.27.0-beta.6`: ``` plumb release: cannot read back .../v1/releases/beta/vv0.27.0-beta.6/seal.json: 404 ``` Every prerelease binary looked for a doubled prefix and refused the release it was running. It appeared the **first time a release was generated by an exact point** — the first time this path had ever executed, since the bootstrap it belongs to landed one commit earlier and could not run until a channel pointer existed. The run that found it also proves the rest works: ``` installed plumb v0.27.0-beta.6 to /tmp/plumb-v0.27.0-beta.6/bin ``` The lane read the pointer and installed the newest published exact rather than canonical stable, which is the whole of what the bootstrap is for.
Stop adding a v the version already carries
All checks were successful
guard / guard (pull_request) Successful in 2m51s
Details
951122acff 
The generator built the URL of its own published seal as `v{running}`, and
`plumb::version!` already yields `v0.27.0-beta.6`. Every prerelease binary
therefore looked for `.../beta/vv0.27.0-beta.6/seal.json` and refused the
release it was running.

It appeared the first time a release was generated by an exact point, which is
the first time this code path had ever executed — the bootstrap it belongs to
landed one commit earlier and could not run until a channel pointer existed.
The run that found it is the one that proves the rest of the mechanism works:
the lane read the pointer and installed `v0.27.0-beta.6` rather than canonical
stable, which is the whole of what the bootstrap is for.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
All checks were successful
guard / guard (pull_request) Successful in 2m51s
Details
This pull request has changes conflicting with the target branch.
  • plumb.toml
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin task/the-version-already-carries-its-v:task/the-version-already-carries-its-v
git switch task/the-version-already-carries-its-v
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!361
No description provided.