Set the v2.0.0 release date in the release notes - #555
Merged
Conversation
The entry still read "TBD 2026" after the release went out. v2.0.0 was published on Aug 25, 2026, matching the tag.
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.
release.notes.mdstill reads_TBD 2026._for the v2.0.0 entry, which went out with the release and is now linked from the project website in two places.v2.0.0 was published Aug 25, 2026 (
2026-08-25T17:37:42Z), matching the tag. Formatted to match the date style already used by the older entries in the file.One-line change; no other
TBDremains in the file.