docs(changelog): restore the 0.1.0 heading and file reproducibility fixes under 0.7.3 - #114
Merged
Merged
Conversation
…ixes under 0.7.3 The first reproducible-build changelog edit accidentally replaced the `## [0.1.0] — 2026-06-05` version heading with a `### Fixed` subsection, so every 0.1.0 entry was left dangling under [Unreleased] and the two reproducibility notes sat as a stray duplicate `### Fixed` block. Restore the 0.1.0 heading and move the reproducibility fixes (the v0.7.1->v0.7.3 Chocolatey checksum saga) into a proper `## [0.7.3] — 2026-06-20` section. Structure only; entry text unchanged. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CZYQWDcCaPU9tpWxVJz5sF
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
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.
Tidy-up of the two loose ends from the Chocolatey reproducibility work. One of them turned out to be a real bug, not cosmetic; the other I'm recommending against — details below.
✅ Done — CHANGELOG (fixes a regression I introduced)
While poking at this I found that the first reproducible-build changelog edit (in #112) accidentally replaced the
## [0.1.0] — 2026-06-05version heading with a### Fixedsubsection. The result:[Unreleased], so the changelog claimed all of 0.1.0 was unreleased; and### Fixedinside[Unreleased].This PR:
## [0.1.0] — 2026-06-05heading, re-parenting its entries correctly; and## [0.7.3] — 2026-06-20section.Structure only — no entry text changed. Result is well-formed and in order:
[Unreleased]→[0.7.3]→[0.1.0].🤖 Generated with Claude Code
https://claude.ai/code/session_01CZYQWDcCaPU9tpWxVJz5sF
Generated by Claude Code