Repository navigation
docs: link published GitHub Releases from the README - #9
Merged
Merged
Conversation
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
2 participants
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.
Adds a short Releases section to the README (right after the Roadmap) linking the two published GitHub Releases and
CHANGELOG.md.Until now nothing in the README pointed at the tagged releases, even though
v0.1.0andv0.2.0are both published. This closes that gap so a first-time visitor lands on the changelog-backed history.Changes
README.md: new "Releases" section with a small table linkingv0.2.0andv0.1.0, plus a pointer toCHANGELOG.md.Docs-only; no code or behavior change. The CI badge and metric-reproduction commands were already present and are left untouched.
Generated by Claude Code