Merge branch 'main' into docs/add-uv-pixi-install-instructions

Author: cluster2600

.coveragerc

@@ -1,9 +1,25 @@
-# SPDX-FileCopyrightText: Copyright (c) 2025 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
+# SPDX-FileCopyrightText: Copyright (c) 2025-2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
 # SPDX-License-Identifier: LicenseRef-NVIDIA-SOFTWARE-LICENSE
 
-[report]
-show_missing = true
+[paths]
+source =
+    cuda\
+    cuda/
 
 [run]
 plugins = Cython.Coverage
 core = ctrace
+branch = False
+relative_files = True
+# Omits specific definition files that causes plugin errors
+omit =
+    */windll.pxd
+    */_lib/windll.pxd
+    */_lib/utils.pxd
+
+[report]
+show_missing = true
+precision = 2
+
+[html]
+show_contexts = True

.github/ISSUE_TEMPLATE/release_checklist.yml

@@ -1,4 +1,4 @@
-# SPDX-FileCopyrightText: Copyright (c) 2024-2025 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
+# SPDX-FileCopyrightText: Copyright (c) 2024-2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
 #
 # SPDX-License-Identifier: Apache-2.0
 
@@ -10,7 +10,7 @@ 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.
+        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).
 
   - type: checkboxes
     id: subpackage-tasks
@@ -20,17 +20,13 @@ body:
         - label: File an internal nvbug to communicate test plan & release schedule with QA
         - label: Ensure all pending PRs are reviewed, tested, and merged
         - label: Check (or update if needed) the dependency requirements
-        - label: Create a public rc tag
-        - label: "Point QA to fetch public artifacts (wheels) from the GHA run ID, example: `gh run download 12323257563 -p \"cuda-core*\" -R NVIDIA/cuda-python`"
-        - label: Wait for QA reports and fix any issues found
         - 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
         - label: If any code change happens, rebuild the wheels from the new tag
-        - label: Update the conda recipe & release conda packages
-        - label: Upload conda packages to nvidia channel
         - label: Upload wheels to PyPI
+        - label: Update the conda recipe & release conda packages
         - label: Post-release QA
         - label: Finalize the announcement update
         - label: Send out the announcement internally

.github/RELEASE-core.md

@@ -0,0 +1,266 @@
+<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. -->
+<!-- SPDX-License-Identifier: Apache-2.0 -->
+
+# cuda.core Release Process
+
+This document covers the `cuda.core` release process. For other packages:
+`cuda-bindings` and `cuda-python` involve a private repository and are not
+documented here; `cuda-pathfinder` is largely automated by the
+[release-cuda-pathfinder.yml](workflows/release-cuda-pathfinder.yml)
+workflow.
+
+Each section below provides detailed guidance for a step in the
+[Release Checklist](ISSUE_TEMPLATE/release_checklist.yml). To start a
+release, create a new issue from that template and work through it item by
+item, referring back here as needed.
+
+---
+
+## File an internal nvbug
+
+Create an nvbug to request that SWQA begin post-release validation.  Issues
+identified by that process are typically addressed in a patch release.  To find
+the template, search for a previous release's nvbug (e.g. by title "Release of
+cuda.core") and create a new bug from the same template.
+
+Example:
+
+> **Title:** Release of cuda.core v0.6.0
+>
+> **Description:**
+>
+> Requesting SWQA validation for the cuda.core v0.6.0 release. Please test
+> the following SW combinations on all listed platforms and report any
+> issues found.
+>
+> **SW Combinations**
+> - cuda.core 0.6.0 / cuda.bindings 12.9 / CTK 12.9 / CUDA 12.9 driver
+> - cuda.core 0.6.0 / cuda.bindings 13.0 / CTK 13.0 / CUDA 13.0 driver
+> - cuda.core 0.6.0 / cuda.bindings 13.1 / CTK 13.1 / CUDA 13.1 driver
+>
+> **Platforms**
+> - Linux x86-64
+> - Linux arm64
+> - Windows x86-64 (TCC and WDDM)
+> - WSL
+>
+> **Test Plan**
+>
+> Functional tests as described in the cuda.core test plan.
+>
+> **Release Milestones**
+> - Pre-release QA (this request)
+> - GitHub release tag and posting
+> - PyPI wheel upload
+> - Post-release validation
+
+Update the version, SW combinations (check with the release owner), and
+platforms as appropriate for each release.
+
+---
+
+## Check (or update if needed) the dependency requirements
+
+Review `cuda_core/pyproject.toml` and verify that all dependency
+requirements are current.
+
+---
+
+## Finalize the doc update, including release notes
+
+Review every PR included in the release. For each one, check whether new
+functions, classes, or features were added and whether they have complete
+docstrings. Add or edit docstrings as needed — touching docstrings and
+type annotations in code is OK during code freeze.
+
+Write the release notes in `cuda_core/docs/source/release/`. Look at
+historical release notes for guidance on format and structure. Balance all
+entries for length, specificity, tone, and consistency. Highlight a few
+notable items in the highlights section, keeping their full entries in the
+appropriate sections below.
+
+---
+
+## Update the docs for the new version
+
+Add the new version to
+`cuda_core/docs/nv-versions.json`. This file drives the version
+switcher on the documentation site. Add an entry for the new version
+after `"latest"`, following the existing pattern. The docs themselves are
+built and deployed automatically by the release workflow.
+
+---
+
+## Create a public release tag
+
+**Warning:** Pushing a tag is a potentially irrevocable action.  Be absolutely
+certain the tag points to the correct commit before pushing.
+
+Tags should be GPG-signed. The tag name format is `cuda-core-v<VERSION>`
+(e.g. `cuda-core-v0.6.0`). The tag must point to a commit on `main`.
+
+```bash
+git checkout main
+git pull origin main
+git tag -s cuda-core-v0.6.0 -m "cuda-core v0.6.0"
+git push origin cuda-core-v0.6.0
+```
+
+---
+
+## Wait for the tag-triggered CI run to complete
+
+Pushing the tag triggers a CI run automatically. Monitor it in the
+**Actions** tab on GitHub.
+
+- **All CI tests should succeed.** If any fail, investigate and rerun as
+  needed.
+- Note the **run ID** of the successful tag-triggered run. The release
+  workflow can auto-detect it from the tag, but you can also provide it
+  explicitly.
+
+---
+
+## Upload wheels to PyPI
+
+This is a single `CI: Release` workflow run with two sequential stages:
+publish to TestPyPI, then publish the same wheel set to PyPI.
+
+1. Go to **Actions > CI: Release** and run the workflow with:
+   - **Component**: `cuda-core`
+   - **The release git tag**: `cuda-core-v0.6.0`
+
+   The workflow automatically looks up the successful tag-triggered CI run
+   for the selected release tag.
+
+2. Wait for the workflow to complete. It will:
+   - publish the selected wheels to TestPyPI
+   - publish the same wheel set to PyPI
+
+3. After completion, verify the final PyPI upload:
+
+```bash
+pip install cuda-core==0.6.0
+```
+
+---
+
+## Update the conda recipe & release conda packages
+
+The conda-forge feedstock builds from the GitHub Release source archive
+(not from PyPI). There are three approaches to updating the feedstock,
+from least effort to most control.
+
+### Approach A: Wait for the bot
+
+The `regro-cf-autotick-bot` periodically scans for new releases and opens
+a PR automatically. If nothing has changed in the build requirements, the
+bot's PR may be sufficient — review it and ask a feedstock maintainer
+to merge. However, the bot only
+updates the version and sha256. If build dependencies, import paths, or
+other recipe fields have changed, the bot's PR will be incomplete and CI
+will fail.
+
+### Approach B: Request a bot update
+
+If the bot hasn't opened a PR, you can request one explicitly. Go to the
+feedstock's Issues tab and create a new "Bot commands" issue:
+
+- **Title**: `@conda-forge-admin, please update version`
+- **Body**: (leave empty)
+
+This triggers the bot to create a version-bump PR. As with approach A,
+review the PR and push additional fixes if needed.
+
+### Approach C: Manual PR
+
+For full control — or when the bot's PR needs extensive fixes — open a
+PR manually from a fork.
+
+**Fork and clone** (one-time setup):
+
+```bash
+gh repo fork conda-forge/cuda-core-feedstock --clone
+cd cuda-core-feedstock
+```
+
+**Create a branch and edit `recipe/meta.yaml`:**
+
+```bash
+git checkout -b update-v0.6.0 origin/main
+```
+
+Update the following fields:
+
+1. **`version`**: Set to the new version (e.g. `0.6.0`).
+2. **`number`** (build number): Reset to `0` for a new version.
+3. **`sha256`**: The SHA-256 of the source archive from the GitHub
+   Release. Download it and compute the hash:
+
+   ```bash
+   curl -sL https://github.com/NVIDIA/cuda-python/releases/download/cuda-core-v0.6.0/cuda-python-cuda-core-v0.6.0.tar.gz \
+       | sha256sum
+   ```
+
+4. **Host dependencies**: Ensure all build-time dependencies are listed.
+   For example, v0.6.0 added a Cython C++ dependency on `nvrtc.h`,
+   requiring `cuda-nvrtc-dev` in both `host` requirements and
+   `ignore_run_exports_from`.
+
+5. **Test commands and descriptions**: Update any import paths or
+   descriptions that changed (e.g. `cuda.core.experimental` ->
+   `cuda.core`).
+
+**Open a PR:**
+
+```bash
+git add recipe/meta.yaml
+git commit -m "Update cuda-core to 0.6.0"
+git push <your-github-username> update-v0.6.0
+
+gh pr create \
+    --repo conda-forge/cuda-core-feedstock \
+    --head <your-github-username>:update-v0.6.0 \
+    --title "Update cuda-core to 0.6.0" \
+    --body "Update cuda-core to version 0.6.0."
+```
+
+### Notes
+
+The feedstock CI (Azure Pipelines) triggers automatically on the PR.
+Monitor it for build failures — common issues include missing build-time
+header dependencies. Feedstock maintainers (listed in
+`recipe/meta.yaml` under `extra.recipe-maintainers`) can merge the PR.
+
+---
+
+## Post-release QA
+
+*TBD*
+
+---
+
+## Finalize the announcement update
+
+The release workflow creates a draft GitHub Release. To publish it:
+
+1. Go to the repository on GitHub, click **Tags**, then switch to the
+   **Releases** tab.
+2. Find the draft release for the new tag and click **Edit**.
+3. Copy the body from a previous release as a starting point. It
+   typically links to the release notes in the documentation (e.g.
+   `https://nvidia.github.io/cuda-python/cuda-core/latest/release/0.6.0-notes.html`).
+4. Update the link and any version references, then click
+   **Publish release**.
+
+---
+
+## Send out the announcement internally
+
+The release owner will prepare and send the announcement.
+
+---
+
+## Send out the announcement externally (GitHub Release -> Announcement)
+
+*TBD*

.github/actions/fetch_ctk/action.yml

@@ -14,7 +14,7 @@ inputs:
   cuda-components:
     description: "A list of the CTK components to install as a comma-separated list. e.g. 'cuda_nvcc,cuda_nvrtc,cuda_cudart'"
     required: false
-    default: "cuda_nvcc,cuda_cudart,cuda_crt,libnvvm,cuda_nvrtc,cuda_profiler_api,cuda_cccl,libnvjitlink,libcufile,libnvfatbin"
+    default: "cuda_nvcc,cuda_cudart,cuda_crt,libnvvm,cuda_nvrtc,cuda_profiler_api,cuda_cccl,cuda_cupti,libnvjitlink,libcufile,libnvfatbin"
   cuda-path:
     description: "where the CTK components will be installed to, relative to $PWD"
     required: false

.github/copy-pr-bot.yaml

@@ -5,6 +5,6 @@
 # https://docs.gha-runners.nvidia.com/apps/copy-pr-bot/
 
 enabled: true
-# always require manual CI triggering, ignoring signed commits
+# auto-sync ready PRs so CI starts immediately; keep draft PRs manual
 auto_sync_draft: false
-auto_sync_ready: false
+auto_sync_ready: true

.github/dependabot.yml

@@ -4,6 +4,7 @@
 
 version: 2
 updates:
+  # GitHub Actions updates targeting the default branch (main)
   - package-ecosystem: github-actions
     directory: /
     schedule:
@@ -19,3 +20,21 @@ updates:
         applies-to: version-updates
         patterns: ["*"]
         update-types: ["major", "minor", "patch"]
+
+  # GitHub Actions updates targeting the 12.9.x branch
+  - package-ecosystem: github-actions
+    directory: /
+    target-branch: "12.9.x"  # keep in sync with backport_branch in ci/versions.yml
+    schedule:
+      interval: "monthly"
+      time: "09:00"
+      timezone: "America/Los_Angeles"
+
+    # Keep churn down: only one open PR from this ecosystem at a time
+    open-pull-requests-limit: 1
+
+    groups:
+      actions-monthly:
+        applies-to: version-updates
+        patterns: ["*"]
+        update-types: ["major", "minor", "patch"]

.github/workflows/backport.yml

@@ -43,7 +43,7 @@ jobs:
           echo "OLD_BRANCH=${OLD_BRANCH}" >> $GITHUB_ENV
 
       - name: Create backport pull requests
-        uses: korthout/backport-action@c656f5d5851037b2b38fb5db2691a03fa229e3b2  # v4.0.1
+        uses: korthout/backport-action@3c06f323a58619da1e8522229ebc8d5de2633e46  # v4.3.0
         with:
           copy_assignees: true
           copy_labels_pattern: true
@@ -67,7 +67,7 @@ jobs:
         run: echo "BACKPORT_BRANCH=${{ inputs.backport-branch }}" >> $GITHUB_ENV
 
       - name: Create backport pull requests
-        uses: korthout/backport-action@c656f5d5851037b2b38fb5db2691a03fa229e3b2  # v4.0.1
+        uses: korthout/backport-action@3c06f323a58619da1e8522229ebc8d5de2633e46  # v4.3.0
         with:
           copy_assignees: true
           copy_labels_pattern: true