Repository navigation
docs: fold v2.2.1 notes into v2.3.0 - #73
Merged
Merged
Conversation
What/Why #69 added a v2.3.0 section above the v2.2.1 notes from #70 and #71, but only one release is going out. v2.3.0 now carries every entry, and its intro names spec v2.2.0, the current version, instead of v2.1.0. Proof it works Docs only. CHANGELOG.md has one unreleased section. Risk Low. Docs only. AI role Drafted by Claude Opus 5.5 and reviewed by the maintainer. Review focus None. Signed-off-by: jmeridth <jmeridth@gmail.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.
What/Why
#69 added a
v2.3.0section above thev2.2.1notes from #70 and #71, but only one release is going out. This moves those entries intov2.3.0and fixes its intro to name spec v2.2.0 instead of v2.1.0.AI role
Drafted by Claude Opus 5.5 and reviewed by the maintainer.