docs: correct changelog versions and reconstruct 0.1.64-0.1.66 - #71
Merged
Conversation
The overhaul notes were written as [0.1.65], but 0.1.65 and 0.1.66 already exist: the auto-publish trigger removed in #69 cut v0.1.64, v0.1.65 and v0.1.66 in the space of half an hour today, one per merged PR. The overhaul is therefore 0.1.67. Those three releases also all published the same body. The workflow falls back to [Unreleased] when it finds no section for the version it is building, and nobody had renamed the heading between merges, so v0.1.64, v0.1.65 and v0.1.66 each shipped an identical set of notes describing only the release-notes work. Two of the three were wrong about their own contents. This reconstructs a section for each from what the tag actually contains rather than from what was published: 0.1.64 is the release-notes refresh (#66), 0.1.65 the power-plan comparison chart (#67), 0.1.66 the scrollable version history in the upgrade prompt (#68). The published release bodies on GitHub are left alone; this file is now the accurate record, and it is what future upgrade prompts read. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The overhaul notes landed in #70 as
[0.1.65]. That version is taken — the auto-publish trigger removed in #69 cut v0.1.64, v0.1.65 and v0.1.66 in about half an hour today, one per merged PR. The overhaul is0.1.67.Those three releases also all published the same body. The workflow falls back to
[Unreleased]when it finds no section for the version being built, and the heading was never renamed between merges, so all three shipped identical notes describing only the release-notes work. Two of the three were wrong about their own contents.This adds a section for each, reconstructed from what the tag actually contains:
feat/release-notes-refreshfeat/plan-comparison-chartfeat/update-prompt-historyThe published release bodies on GitHub are left as they are. This file is the accurate record going forward, and it is what the upgrade prompt reads.
Docs only — no code change.