Address migration review: simplify configuration and tooling

Signed-off-by: Ralf W. Grosse-Kunstleve <rgrossekunst@nvidia.com>

Author: rwgk

.github/workflows/ci-pixi-source-test.yml

@@ -109,7 +109,7 @@ jobs:
         if: ${{ matrix.cuda-env == 'cu12' }}
         uses: ./.github/actions/setup-hardened-python
         with:
-          python-version: "3.12"
+          python-version: "3.11"
 
       - name: Bootstrap maintenance SCM in this disposable checkout
         if: ${{ matrix.cuda-env == 'cu12' }}
@@ -265,7 +265,7 @@ jobs:
         if: ${{ matrix.cuda-env == 'cu12' }}
         uses: ./.github/actions/setup-hardened-python
         with:
-          python-version: "3.12"
+          python-version: "3.11"
 
       - name: Bootstrap maintenance SCM in this disposable checkout
         if: ${{ matrix.cuda-env == 'cu12' }}

AGENTS.md

@@ -59,20 +59,10 @@ For each package tag namespace and target release `X.Y.Z`:
   existing history.
 - Treat pushed tags as immutable. Correct an unsuitable tagged state with a
   new versioned milestone rather than moving or replacing the existing tag.
-- Reserve a new preview target from the next globally unused release number,
-  checking canonical tags and coordinating releases on every maintenance or
-  stabilization branch. A release on another branch consumes that number even
-  when its tag is not reachable from `main`. Update `scm-bootstrap-release`
-  before another build if such a release consumes its target; do not bump the
-  field per PR or use it to override suitable reachable tags.
-- Moving a package's SCM selector to a new toolkit minor also needs a matching
-  reachable milestone. Updating the selector alone can produce an incorrect
-  placeholder version. Validate previews with local tags in an independent
-  disposable clone until the release history supplies the right milestone.
-- For a newly integrated maintenance root, create its first retained internal
-  milestone only after the integration group has landed and been validated on
-  `main`. Retained tag creation requires an explicit maintainer decision;
-  preparation of a PR stack does not authorize creating or pushing it.
+- Before setting or changing `scm-bootstrap-release`, check canonical tags
+  and coordinate with release maintainers. Use an unused release number,
+  including releases tagged on other branches; keep the same target across
+  builds until release coordination requires a change.
 
 Use the package's established tag namespace, such as `vX.Y.Z...` for
 `cuda-bindings` and `cuda-python`, `cuda-core-vX.Y.Z...` for `cuda-core`, and

README.md

@@ -51,7 +51,7 @@ The list of available interfaces is:
 ## Bindings source roots
 
 Current CUDA 13 bindings live in [`cuda_bindings_13/`](cuda_bindings_13/), and
-CUDA 12.9 sources have a separate
+CUDA 12 bindings sources have a separate
 [developer environment](cuda_bindings_12/README.md). Both roots build the same
 `cuda-bindings` distribution and `cuda.bindings` namespace; develop and test
 them in separate environments.

ci/pyproject.toml

@@ -15,7 +15,7 @@ requires-python = ">=3.11"
 dependencies = [
   "packaging==26.0",
   "PyYAML==6.0.3",
-  "setuptools-scm>=8,!=10.1",
+  "setuptools-scm[simple]>=8,!=10.1",
 ]
 
 [project.optional-dependencies]

cuda_bindings_12/README.md

@@ -23,7 +23,8 @@ pixi run --manifest-path cuda_bindings_12 -e cu12 test
 
 This builds bindings and Cython test extensions from source, then runs the
 GPU test suite. `pixi run -e cu12 test-bindings` selects the same package.
-For an existing Python environment with CUDA 12.9 headers and a compiler:
+For an existing Python environment with CUDA 12.9 headers, a compiler,
+and pip 25.1 or newer:
 
 ```console
 cd cuda_bindings_12
@@ -35,7 +36,7 @@ python -m pytest tests/ tests/cython/
 Use `build_tests.bat` on Windows. Free-threaded Python also needs the
 `test-ft` dependency group.
 
-Versions follow reachable `v12.9.*` tags through standard `setuptools-scm`.
+Versions follow reachable `v12.*` tags through standard `setuptools-scm`.
 Before a retained milestone exists for the reserved preview release, CI uses
 `ci.tools.bindings_scm_version` in its disposable checkout to create one
 local ancestor tag. Never run that helper in a shared development repository
@@ -45,7 +46,8 @@ or push its synthetic tags. See the repository's
 
 ## Testing
 
-Testing dependencies can be installed using the `[test]` optional dependency identifier. For example, `pip install -v -e .[test]`.
+Install the package and its `test` dependency group with
+`python -m pip install -v -e . --group test` (pip 25.1 or newer).
 
 Multiple testing options are available:
 

cuda_bindings_12/docs/source/release/12.X.Y-notes.rst

@@ -5,8 +5,8 @@
 
 .. module:: cuda.bindings
 
-``cuda-bindings`` Upcoming CUDA 12 Release Notes
-================================================
+``cuda-bindings`` 12.X.Y Release notes
+======================================
 
 Unreleased
 

cuda_bindings_12/pyproject.toml

@@ -47,14 +47,6 @@ all = [
     "nvidia-cufile-cu12; sys_platform == 'linux'",
 ]
 
-test = [
-    "cython>=3.2.5,<3.3",
-    "setuptools>=80.0.0",
-    "numpy>=1.21.1",
-    "pytest==9.1.0",
-    "pytest-benchmark>=3.4.1",
-    "pyglet>=2.1.9"
-]
 
 [dependency-groups]
 # Keep build in sync with build-system.requires.
@@ -151,7 +143,7 @@ exclude = ["cuda/bindings/_version.py"]
 [tool.setuptools_scm]
 root = ".."
 version_file = "cuda/bindings/_version.py"
-git_describe_command = ["git", "describe", "--dirty", "--tags", "--long", "--match", "v12.9.*"]
+git_describe_command = ["git", "describe", "--dirty", "--tags", "--long", "--match", "v12.*"]
 
 [tool.cuda-python]
 scm-bootstrap-release = "12.9.11"

cuda_bindings_13/README.md

@@ -20,7 +20,8 @@ Debuggable builds are not supported on Windows.
 
 ## Testing
 
-Testing dependencies can be installed using the `[test]` optional dependency identifier. For example, `pip install -v -e .[test]`.
+With pip 25.1 or newer, install testing dependencies using the `test`
+dependency group: `python -m pip install -v -e . --group test`.
 
 Multiple testing options are available: