Add CHANGELOG - #84
Merged
Merged
Conversation
Every published version with its date and release notes, so anyone upgrading can see what changed without reading git history. Co-Authored-By: Claude Opus 5 (1M context) <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.
Generated from this repo's GitHub Releases: every published version with its date and release notes, newest first.
Anyone upgrading a published package currently has to read git history or click through the Releases page to find out what changed. This puts it in the repo where people look for it.
Nothing is invented - each entry is the release body as written, with headings demoted one level so they nest under the version. Each entry links back to its release.
🤖 Generated with Claude Code