Update version numbers to prepare for v2.1 release#250
Merged
Conversation
ngoldbaum
force-pushed
the
update-2.1-version-numbers
branch
from
adf44f6 to
2a462c3
Compare
Contributor
Author
|
I triggered a "full" CI run on my fork. Everything passes except for the TSan CI, which I think should be fixed by #251. |
mattip
reviewed
Jun 30, 2026
mattip
reviewed
Jun 30, 2026
mattip
reviewed
Jun 30, 2026
mattip
left a comment
mattip
left a comment
Contributor
There was a problem hiding this comment.
LGTM, a few small nits so this is less painful next time.
Contributor
Author
|
The CI failure is another flaky test that should be marked as thread-unsafe: #252 |
Contributor
|
I think the failing test will be fixed by #252. Everything else looks good |
Contributor
|
Thanks @ngoldbaum |
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
2 participants
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.
I also updated a few stray spots referring to Python versions that are no longer supported.
A maintainer will need to create a
release-2.1branch after this is merged.