release: carry the v0.8.0 notes in the release that delivers them #52

Open
PerishFire wants to merge 1 commit from land/repo/changelog-fold into main
Owner

Why

plumb ship binary dispatch --version v0.8.1-beta.1 refused:

plumb release: candidate mutates frozen changelog v0.8.0 while releasing v0.8.1

The changelog proof compares the candidate against the previous release, and
previous reads /v1/channels/stable.json — still naming v0.7.0, because
v0.8.0 published but never activated (PerishLab/plumb#346). Across that span
docs/CHANGELOG/v0.8.0/ is an addition, and a release may not touch another
version's changelog.

The refusal is right, and the state it caught is the honest one: v0.8.0 reached
no consumer through stable, so the release that actually delivers its content
is v0.8.1.

What

  • docs/CHANGELOG/v0.8.0/ folds into v0.8.1/ and is removed. v0.7.0's commit
    never held that directory either, so the diff the proof reads no longer
    mentions it at all.
  • The v0.8.1 migration inlines what it previously referenced by path, so no
    reader is sent to a file this commit deletes.

v0.8.0's published objects and seal are untouched.

Tests

ectropy . clean, plumb doctor . zero out of true.

## Why `plumb ship binary dispatch --version v0.8.1-beta.1` refused: ``` plumb release: candidate mutates frozen changelog v0.8.0 while releasing v0.8.1 ``` The changelog proof compares the candidate against the previous release, and `previous` reads `/v1/channels/stable.json` — still naming v0.7.0, because v0.8.0 published but never activated (PerishLab/plumb#346). Across that span `docs/CHANGELOG/v0.8.0/` is an addition, and a release may not touch another version's changelog. The refusal is right, and the state it caught is the honest one: v0.8.0 reached no consumer through `stable`, so the release that actually delivers its content is v0.8.1. ## What - `docs/CHANGELOG/v0.8.0/` folds into `v0.8.1/` and is removed. v0.7.0's commit never held that directory either, so the diff the proof reads no longer mentions it at all. - The v0.8.1 migration inlines what it previously referenced by path, so no reader is sent to a file this commit deletes. v0.8.0's published objects and seal are untouched. ## Tests `ectropy .` clean, `plumb doctor .` zero out of true.
release: carry the v0.8.0 notes in the release that delivers them
All checks were successful
guard / guard (pull_request) Successful in 1m27s
aa332959e5
## Why

`plumb ship binary dispatch --version v0.8.1-beta.1` refused:

```
plumb release: candidate mutates frozen changelog v0.8.0 while releasing v0.8.1
```

The changelog proof compares the candidate against the previous release, and
`previous` reads `/v1/channels/stable.json` — still naming v0.7.0, because
v0.8.0 published but never activated (PerishLab/plumb#346). Across that span
`docs/CHANGELOG/v0.8.0/` is an addition, and a release may not touch another
version's changelog.

The refusal is right, and the state it caught is the honest one: v0.8.0 reached
no consumer through `stable`, so the release that actually delivers its content
is v0.8.1.

## What

- `docs/CHANGELOG/v0.8.0/` folds into `v0.8.1/` and is removed. v0.7.0's commit
  never held that directory either, so the diff the proof reads no longer
  mentions it at all.
- The v0.8.1 migration inlines what it previously referenced by path, so no
  reader is sent to a file this commit deletes.

v0.8.0's published objects and seal are untouched.

## Tests

`ectropy .` clean, `plumb doctor .` zero out of true.

Land-Source: repo/changelog-fold@40568d6c87
All checks were successful
guard / guard (pull_request) Successful in 1m27s
Required
Details
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin land/repo/changelog-fold:land/repo/changelog-fold
git switch land/repo/changelog-fold
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
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
PerishFire/sidecar!52
No description provided.