-
Notifications
You must be signed in to change notification settings - Fork 54
Bump version to 0.24.0 #716
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
- Add arch specific target support (NVIDIA#549) - chore: disable `locked` flag to bypass prefix-dev/pixi#5256 (NVIDIA#714) - ci: relock pixi (NVIDIA#712) - ci: remove redundant conda build in ci (NVIDIA#711) - chore(deps): bump numba-cuda version and relock pixi (NVIDIA#707) - Dropping bits in the old CI & Propagating recent changes from cuda-python (NVIDIA#683) - Fix `test_wheel_deps_wheels.sh` to actually uninstall `nvvm` and `nvrtc` packages for CUDA 13 (NVIDIA#701) - perf: remove some exception control flow and buffer-exception penalization for arrays (NVIDIA#700) - perf: let CAI fall through instead of calling from_cuda_array_interface (NVIDIA#694) - chore: perf lint (NVIDIA#697) - chore(deps): bump deps in pixi lockfile (NVIDIA#693) - fix: use freethreading-supported `_PySet_NextItemRef` where possible (NVIDIA#682) - Support python `3.14` (NVIDIA#599) - Remove customized address space tracking and address class emission in debug info (NVIDIA#669) - Drop `experimental` from cuda.core namespace imports (NVIDIA#676) - Remove dangling references to NUMBA_CUDA_ENABLE_MINOR_VERSION_COMPATIBILITY (NVIDIA#675) - Use `rapidsai/sccache` in CI (NVIDIA#674) - chore(dev-deps): remove ipython and pyinstrument (NVIDIA#670) - Set up a new VM-based CI infrastructure (NVIDIA#604)
|
Auto-sync is disabled for ready for review pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
|
/ok to test |
Greptile OverviewGreptile SummaryThis PR bumps the version from 0.23.0 to 0.24.0, consolidating approximately 20 merged PRs since the last release. The changes include: Key Features and Improvements:
Breaking Changes:
Infrastructure Updates:
Version Update Coverage:
The version is dynamically read from the VERSION file by Confidence Score: 5/5
Important Files ChangedFile Analysis
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1 file reviewed, 1 comment
| @@ -1 +1 @@ | |||
| 0.23.0 | |||
| 0.24.0 | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The version in pixi.toml (line 275) also needs to be updated from 0.23.0 to 0.24.0 to maintain consistency with the VERSION file.
Based on the git history, previous version bumps (e.g., commits #707 and #641) also updated the pixi.toml file. This appears to have been missed in this PR.
| 0.24.0 | |
| 0.24.0 |
Additionally, after updating pixi.toml, you should run:
pixi updateto regenerate pixi.lock with the new version references.
|
/ok to test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1 file reviewed, 1 comment
| [package] | ||
| name = "numba-cuda" | ||
| version = "0.23.0" | ||
| version = "0.24.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The pixi.lock file needs to be updated to reflect the version bump to 0.24.0. Currently, pixi.lock contains 15 references to version 0.23.0 that should be updated to 0.24.0.
Based on historical version bump patterns:
- PR chore(deps): bump numba-cuda version and relock pixi #707 ("chore(deps): bump numba-cuda version and relock pixi") updated both
pixi.tomlandpixi.lock - PR chore: bump version in pixi.toml #641 ("chore: bump version in pixi.toml") also updated both files
The lockfile should be regenerated using pixi install or similar command to ensure all version references are consistent with this bump.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No files reviewed, no comments
lockedflag to bypass lockfile reported as out of date with--lockedeven after runningpixi lockprefix-dev/pixi#5256 (chore: disablelockedflag to bypass https://github.com/prefix-dev/pixi/issues/5256 #714)test_wheel_deps_wheels.shto actually uninstallnvvmandnvrtcpackages for CUDA 13 (Fixtest_wheel_deps_wheels.shto actually uninstallnvvmandnvrtcpackages for CUDA 13 #701)_PySet_NextItemRefwhere possible (fix: use freethreading-supported_PySet_NextItemRefwhere possible #682)3.14(Support python3.14#599)experimentalfrom cuda.core namespace imports (Dropexperimentalfrom cuda.core namespace imports #676)rapidsai/sccachein CI (Userapidsai/sccachein CI #674)