Repository navigation
chore(release): 2.0.0 - #431
Merged
Merged
Conversation
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.
Closes #430.
Prepare v2.0.0 from
release/2.0as it stands: v2.0.0-rc.8 plus the README split (#416). No code changes.pyproject.toml:2.0.0-rc.8→2.0.0uv.lock:cldkentry2.0.0rc7→2.0.0(rc.8's bump never refreshed the lock;uv lockchanged only this line)CHANGELOG.md: newv2.0.0section. It lists what breaks for code written against 1.5.0, each with a migration step, and points back to the rc sections, which are unchanged. It leaves out changes to 2.0-only APIs (LocateResult,paths_between,TSSpan), since 1.5.0 callers never saw them.Deferred to 2.0.x: #421, and the pin bumps #413, #423, #427, #428 and #429.