Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion numba_cuda/VERSION
Original file line number Diff line number Diff line change
@@ -1 +1 @@
0.23.0
0.24.0
Copy link
Contributor

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.

Suggested change
0.24.0
0.24.0

Additionally, after updating pixi.toml, you should run:

pixi update

to regenerate pixi.lock with the new version references.

60 changes: 30 additions & 30 deletions pixi.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion pixi.toml
Original file line number Diff line number Diff line change
Expand Up @@ -272,7 +272,7 @@ NUMBA_ENABLE_CUDASIM = "1"

[package]
name = "numba-cuda"
version = "0.23.0"
version = "0.24.0"
Copy link
Contributor

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:

The lockfile should be regenerated using pixi install or similar command to ensure all version references are consistent with this bump.


[package.build]
backend = { name = "pixi-build-python", version = "*" }
Expand Down
Loading