release: carry the v0.8.0 notes in the release that delivers them #52
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "land/repo/changelog-fold"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
plumb ship binary dispatch --version v0.8.1-beta.1refused:The changelog proof compares the candidate against the previous release, and
previousreads/v1/channels/stable.json— still naming v0.7.0, becausev0.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 anotherversion'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 contentis v0.8.1.
What
docs/CHANGELOG/v0.8.0/folds intov0.8.1/and is removed. v0.7.0's commitnever held that directory either, so the diff the proof reads no longer
mentions it at all.
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.View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.