Repository navigation
CHANGELOG: #101 is unreleased, not part of 0.9.1 - #104
Merged
Merged
Conversation
#101 merged into develop after the 0.9.1 release, and the merge placed its bullets under the renamed [0.9.1] heading. v0.9.1 does not contain it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Merged
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.
#101 merged into develop just after the 0.9.1 release (#102). Because the release renamed
[Unreleased]to[0.9.1], the merge put #101's bullets under the 0.9.1 heading.v0.9.1does not contain #101 (git merge-base --is-ancestor 6e261b9 v0.9.1is false). This PR moves those bullets back under[Unreleased]and changes no text.node scripts/changelog-coverage.mjs --head origin/developpasses once it's in.🤖 Generated with Claude Code