dev: update numba-cuda version

[cpcloud]

Update project version

Summary

• Bumped numba-cuda version from 0.20.1 to 0.22.0 in pixi.toml

Changes

• Updated pixi.toml to reflect version 0.22.0s

[copy-pr-bot]

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.

[cpcloud]

/ok to test

[gmarkall]

Is there a way to get this from numba_cuda/VERSION so it doesn't need a separate update?

[cpcloud]

Unfortunately, no. We should just create a version bumping script that does it for all the files we care about containing the correct version.

[cpcloud]

There are a number of tools that do this quite well.

[cpcloud]

prefix-dev/pixi#2946 is the upstream pixi issue.

[greptile-apps]

Greptile Overview

Greptile Summary

Updated numba-cuda version from 0.20.1 to 0.22.0 in pixi.toml and regenerated the lockfile with compatible dependency build hashes.

Key changes:

• Version bump in pixi.toml:251 aligns with the existing version in numba_cuda/VERSION file (0.22.0)
• Lockfile regenerated across all 16+ environments (various Python versions 3.10-3.13 and CUDA versions 12.0-13.0)
• Build hashes updated for all platform variants (linux-64, linux-aarch64, win-64)
• Removed explicit subdir fields in lockfile entries (simplified format)
• Lockfile changes include adding target_platform variant to package metadata

Impact:

• No external dependency version changes - only internal package build metadata updated
• All environments remain compatible with existing dependency constraints

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• Version bump is straightforward metadata change that synchronizes pixi.toml with the actual package version. Lockfile regeneration is standard practice after version changes and only updates build hashes without modifying dependency versions or introducing breaking changes.
• No files require special attention

Important Files Changed

File Analysis

Filename	Score	Overview
pixi.toml	5/5	Version bumped from 0.20.1 to 0.22.0 in package metadata
pixi.lock	5/5	Lockfile regenerated with updated build hashes and removed explicit subdir fields across all environments

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant Pixi as pixi.toml
    participant Lock as pixi.lock
    participant Build as Build System
    participant Pkg as Package Metadata

    Dev->>Pixi: Update version 0.20.1 → 0.22.0
    Note over Pixi: [package] version = "0.22.0"
    
    Dev->>Build: Run pixi lock/update
    Build->>Pkg: Read package metadata
    Pkg-->>Build: Return dependencies & constraints
    
    Build->>Lock: Regenerate lockfile
    Note over Lock: Update build hashes for all environments<br/>(py310-py313, cu12.0-cu13.0, all platforms)
    Lock-->>Lock: Add target_platform variants
    Lock-->>Lock: Remove explicit subdir fields
    Lock-->>Build: Lockfile updated
    
    Build-->>Dev: Version synchronized across 16+ environments

Loading

[greptile-apps]

_{1 file reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}

[cpcloud]

I will do the dependency version updates in a separate PR, and just include the numba-cuda update here.

[cpcloud]

/ok to test

[greptile-apps]

_{1 file reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}

[cpcloud]

/ok to test

[greptile-apps]

_{1 file reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}