ENH: update package version to 12.9.7 (target branch 12.9)

[conda-forge-admin]

This PR was originally created by:

Hi! This is the friendly automated conda-forge-webservice.

It was manually repurposed for the version 12.9.7 release.

---

Fixes #193

Summary

This updates the 12.9 maintenance branch to build and publish the CUDA Python 12.9.7 patch release on conda-forge.

The upstream GitHub release is public and includes the expected source archive:

https://github.com/NVIDIA/cuda-python/releases/download/v12.9.7/cuda-python-v12.9.7.tar.gz
sha256: 9df6ff7121e11b158730ef39350c111728c9d1a2450124f463f7f4026c89d42f

Changes

• Bump recipe/meta.yaml from 12.9.6 to 12.9.7.
• Update the source archive checksum for cuda-python-v12.9.7.tar.gz.
• Require cuda-pathfinder >=1.5.5,<2 for the cuda-bindings runtime dependency.

cuda-pathfinder rationale

The cuda-pathfinder lower bound is intentionally raised for this patch release. Although upstream cuda-bindings 12.9.7 still declares cuda-pathfinder ~=1.1, newer cuda-pathfinder releases contain several CUDA Toolkit 12 discovery fixes that are beneficial for conda users and are not expected to be breaking in this context.

Notable post-1.1 fixes and improvements include:

• Conda-specific dynamic library search in load_nvidia_dynamic_lib(), making conda environment discovery more predictable.
• CTK root canary probing for non-standard-path libraries, notably nvvm.
• CTK canary fallback for header discovery.
• CUPTI dynamic library support for CUDA 12 and 13 in site-packages, conda environments, and CTK installations.
• Static library discovery APIs for CUDA static libraries.
• Windows CUDA 12 cudadevrt conda static-library discovery under Library/lib.

(Pinning to >=1.5.5 also avoids the short-lived 1.3.5 exception behavior regression, which was corrected in 1.4.0.)

Notes

This PR is based on the feedstock 12.9 branch, matching the previous cuda-python v12.9.6 PR. The existing CUDA 12 recipe structure is otherwise left unchanged, including the CUDA 12 dependency ranges and cuda-nvcc-impl usage.

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

• ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.

  • For the test.requires section of <output 0 output, you should usually use the pin python {{ python_min }} for the python entry.

• If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

• ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.
• ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.
• ℹ️ cuda-python output overrides versions pinned in the feedstock:
  ['- In section host: python 9999.*']
  Requirement spec should not list version specifiers to respect conda-forge-pinning. If you need to force another version, please override the pin via conda_build_config.yaml.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/26547554816. Examine the logs at this URL for more detail.}

[conda-forge-admin]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• azure: passed

Thus the PR was passing and merged! Have a great day!