Route independent bindings releases from tagged source configuration

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

Author: rwgk

.github/ISSUE_TEMPLATE/release_checklist.yml

@@ -10,25 +10,26 @@ body:
   - type: markdown
     attributes:
       value: |
-        This checklist is for cuda-core releases as well as cuda-bindings patches. Please go through this checklist and ensure all tasks are completed. See [RELEASE-core.md](../RELEASE-core.md) for detailed guidance on each step (cuda.core).
+        This checklist is for cuda-core releases as well as cuda-bindings patches. See [RELEASE-core.md](../RELEASE-core.md) for cuda.core and [RELEASE-bindings.md](../RELEASE-bindings.md) for bindings release scope, stabilization branches, and validation.
 
   - type: checkboxes
     id: subpackage-tasks
     attributes:
       label: Tasks for cuda-core and cuda-bindings patch release
       options:
         - label: File an internal nvbug to communicate test plan & release schedule with QA
-        - label: Ensure all pending PRs are reviewed, tested, and merged
+        - label: Record the release scope and ensure all PRs selected for this release are reviewed, tested, and merged
         - label: Check (or update if needed) the dependency requirements
         - label: Sweep deprecations whose stated removal version has arrived (`grep -rn 'deprecated::' cuda_core/cuda`) and remove any that are due
         - label: "Finalize the doc update, including release notes (\"Note: Touching docstrings/type annotations in code is OK during code freeze, apply your best judgement!\")"
         - label: Update the docs for the new version
-        - label: Create a public release tag
-        - label: Wait for the tag-triggered CI run to complete, and use that run ID for release workflows (this will upload the release to PyPI)
+        - label: Record the exact source commit, workflow control revision, and selected package root before creating the approved public release tag
+        - label: Wait for the exact tag-triggered CI run to pass and complete a release dry run before approving publication
         - label: Publish the release at https://github.com/NVIDIA/cuda-python/releases (this will trigger the conda package update)
         - label: Approve the conda-package update PR
         - label: Post-release QA
         - label: Finalize the announcement update
         - label: Send out the announcement internally (on `#swcuda-python`)
         - label: Send out the announcement externally (GitHub Release -> Announcement)
-        - label: For a `cuda-bindings` release, make sure MAJOR and MAJOR-1 releases are made, as well as releases of `cuda-python` for MAJOR and MAJOR-1
+        - label: For a `cuda-bindings` release, confirm which supported release lines are in scope using `ci/versions.yml`, and release the matching `cuda-python` package for each planned line
+        - label: For a bindings stabilization or emergency branch, link the PRs returning applicable fixes to `main` and record their applicability to both bindings roots

.github/RELEASE-core.md

@@ -20,12 +20,14 @@ version, then publishes to PyPI and verifies again before publishing the
 GitHub Release without marking it as latest. A failed
 docs build prevents asset uploads, package publication, and finalization.
 
-The release-note checker runs from `git-tag`, not the workflow revision.
-For Pathfinder, that tag must contain a version
-of `ci/tools/check_release_notes.py` that writes `version=<VERSION>` to
-`GITHUB_OUTPUT`. The release-notes job rejects an empty version before
-documentation, asset uploads, or package publication can start. Pathfinder
-package publication also requires successful draft metadata preparation.
+The workflow revision supplies the release tools; release notes and the
+package registry (`ci/versions.yml`) come from `git-tag`. Current tooling
+requires a schema-2 registry in the tagged source. The release-notes job
+exports the checked version and rejects an empty version before documentation,
+asset uploads, or package publication can start. Pathfinder package
+publication also requires successful draft metadata preparation.
+For tags that predate the registry, use compatible historical release tooling;
+do not move existing tags to add the registry or updated tools.
 
 The default `dry-run` action validates preparation, builds docs, and
 collects release artifacts without creating a GitHub Release or publishing

.github/workflows/release-upload.yml

@@ -23,6 +23,11 @@ on:
         type: boolean
         required: false
         default: false
+      bindings-package:
+        description: "Resolved CUDA bindings package JSON"
+        type: string
+        required: false
+        default: ""
 
 concurrency:
   # Keep upload locks component-specific and separate from the caller's workflow lock.
@@ -40,12 +45,33 @@ jobs:
     runs-on: ubuntu-latest
     env:
       ARCHIVE_NAME: ${{ github.event.repository.name }}-${{ inputs.git-tag }}
+      RELEASE_COMPONENT: ${{ inputs.component }}
+      RELEASE_GIT_TAG: ${{ inputs.git-tag }}
+      RELEASE_REPOSITORY: ${{ github.repository }}
+      RELEASE_RUN_ID: ${{ inputs.run-id }}
     steps:
-      - name: Checkout Source
+      - name: Checkout release control plane
         uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1  # v7.0.1
         with:
           fetch-depth: 1
-          ref: ${{ inputs.git-tag }}
+          fetch-tags: true
+
+      - name: Checkout release source
+        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1  # v7.0.1
+        with:
+          ref: refs/tags/${{ inputs.git-tag }}
+          path: release-source
+
+      - name: Set up Python
+        uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97  # v7.0.0
+        with:
+          python-version: "3.12"
+
+      - name: Harden pip
+        uses: ./.github/actions/harden-pip
+
+      - name: Install CI tool dependencies
+        run: python -m pip install -e ./ci
 
       - name: Create Release Directory
         run: mkdir -p release
@@ -54,44 +80,56 @@ jobs:
         run: >
           git archive
           --format=tar.gz
-          --prefix="${{ env.ARCHIVE_NAME }}/"
-          --output="release/${{ env.ARCHIVE_NAME }}.tar.gz"
-          ${{ inputs.git-tag }}
+          --prefix="$ARCHIVE_NAME/"
+          --output="release/$ARCHIVE_NAME.tar.gz"
+          "refs/tags/$RELEASE_GIT_TAG"
 
       - name: Compute Checksum
         run: >
-          sha256sum "release/${{ env.ARCHIVE_NAME }}.tar.gz"
+          sha256sum "release/$ARCHIVE_NAME.tar.gz"
           | awk '{print $1}'
-          > "release/${{ env.ARCHIVE_NAME }}.tar.gz.sha256sum"
+          > "release/$ARCHIVE_NAME.tar.gz.sha256sum"
 
       - name: Upload Archive
         if: ${{ !inputs.dry-run }}
         env:
           GH_TOKEN: ${{ github.token }}
         run: >
           gh release upload
-          --clobber "${{ inputs.git-tag }}"
-          --repo "${{ github.repository }}"
+          --clobber "$RELEASE_GIT_TAG"
+          --repo "$RELEASE_REPOSITORY"
           release/*
 
       - name: Download and Validate Wheels
         env:
+          BINDINGS_PACKAGE: ${{ inputs.bindings-package }}
           GH_TOKEN: ${{ github.token }}
         run: |
           # Use the shared script to download wheels
-          ./ci/tools/download-wheels "${{ inputs.run-id }}" "${{ inputs.component }}" "${{ github.repository }}" "release/wheels"
+          ./ci/tools/download-wheels \
+            "$RELEASE_RUN_ID" \
+            "$RELEASE_COMPONENT" \
+            "$RELEASE_REPOSITORY" \
+            "release/wheels" \
+            "$RELEASE_GIT_TAG" \
+            "$BINDINGS_PACKAGE"
 
           # Validate that release wheels match the expected version from tag.
-          ./ci/tools/validate-release-wheels "${{ inputs.git-tag }}" "${{ inputs.component }}" "release/wheels"
+          python -m ci.tools.validate_release_wheels \
+            "$RELEASE_GIT_TAG" \
+            "$RELEASE_COMPONENT" \
+            "release/wheels" \
+            --bindings-package "$BINDINGS_PACKAGE" \
+            --release-source-root release-source
 
       - name: Upload Wheels
         if: ${{ !inputs.dry-run }}
         env:
           GH_TOKEN: ${{ github.token }}
         run: |
           if [[ -d "release/wheels" && $(ls -A release/wheels 2>/dev/null | wc -l) -gt 0 ]]; then
-            echo "Uploading wheels to release ${{ inputs.git-tag }}"
-            gh release upload --clobber "${{ inputs.git-tag }}" --repo "${{ github.repository }}" release/wheels/*
+            echo "Uploading wheels to release $RELEASE_GIT_TAG"
+            gh release upload --clobber "$RELEASE_GIT_TAG" --repo "$RELEASE_REPOSITORY" release/wheels/*
           fi
 
       - name: Upload dry-run release artifacts