Say what else 0.3.0 carries - #3
Merged
Merged
Conversation
The perf work landed on main between the release section being written and the branch being merged, so the summary paragraph named three of the four things in it. The entries were already there; only the first sentence a reader of the Release page sees was short. Co-Authored-By: Claude Opus 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
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.
The discovery and liveness perf work landed on main between the 0.3.0 section being written and the release branch being merged. Its entries merged into the section correctly; only the summary paragraph — the first sentence anyone reading the Release page sees — was written before it existed.
One line. Cut before the 0.3.0 tag.