Repository navigation
CHANGELOG.md: every release, out of the README - #108
Merged
Merged
Conversation
…v0.3.17's entry The README's status listed each release inline and stopped at v0.3.16; the list now lives in CHANGELOG.md, newest first, written from the tag messages (v0.1.0-rc.1 to v0.3.16) with v0.3.17's entry for the docs work. The README points at it and pins v0.3.17; CONTRIBUTING.md and CLAUDE.md say a release adds its entry and a GitHub release. Co-Authored-By: Claude Opus 5.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
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.
What
After the merge: tag
v0.3.17on main and publish its GitHub release (the newest GitHub release is still 0.2.1).Gates
Markdown only: no tests run, and CI skips it.
🤖 Generated with Claude Code