Add 2025.12 to allowed array API versions #4645
Merged
+6
−2
Conversation
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
8 tasks
Liam-DeVoe
approved these changes
Jan 24, 2026
Member
Liam-DeVoe
left a comment
Liam-DeVoe
left a comment
There was a problem hiding this comment.
Thanks Evgeni! I'll wait for Zac to double check here.
Member
|
Thanks again! |
Contributor
Author
|
Thank you folks! Both for unblocking us downstream, and for the hypothesis itself. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Similar to #4262, which added support for the 2024.12 revision of the Array API standard, this slightly pre-emptive PR adds "2025.12" to the list of recognized Array API versions.
This version is going to be released "soon", and since our testing heavily relies on hypothesis, this patch would help us with bootstrapping tests of new features of the 2025.12 spec.
Previous PRs of this sort (neither caused problems or required follow-up changes):
#3901 added support for 2023.12
#4262 added support for 2024.12