Merge remote-tracking branch 'upstream/main' into cp1458-async-nvml-events

Resolved cuda_core/docs/source/release/1.3.0-notes.rst: kept both the
PR's wait_async entry and upstream's host_launch entry under New features.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: 0z5a <dezhen.lu@student.uni-tuebingen.de>

Author: 0z5a

.clang-format

@@ -0,0 +1,39 @@
+# SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
+#
+# SPDX-License-Identifier: Apache-2.0
+
+# A clang-format style derived from Python's PEP 7 (4-space indent, Stroustrup braces,
+# return type on its own line), except that the column limit is 120 rather than 79.
+# Based on https://gist.github.com/pganssle/0e3a5f828b4d07d79447f6ced8e7e4db
+BasedOnStyle: Google
+BreakAfterReturnType: AllDefinitions
+AllowShortIfStatementsOnASingleLine: Never
+BreakBeforeBraces: Stroustrup
+ColumnLimit: 120
+DerivePointerAlignment: false
+IndentWidth: 4
+Language: Cpp
+PointerAlignment: Right
+ReflowComments: Always
+SpaceBeforeParens: ControlStatements
+SpacesInParens: Never
+TabWidth: 4
+UseTab: Never
+
+# Keep include order as written; reordering can break order-sensitive builds.
+SortIncludes: {Enabled: false}
+
+# Ruff-like wrapping: break after "(", indent arguments, put ")" on its own line.
+# This does not contradict PEP7, but extends it to the consistent style where
+# calls either fit on a single line or they are broken across multiple lines with
+# one argument per line (indented).
+AlignAfterOpenBracket: true
+BreakAfterOpenBracketBracedList: true
+BreakAfterOpenBracketFunction: true
+BreakAfterOpenBracketIf: true
+BreakBeforeCloseBracketBracedList: true
+BreakBeforeCloseBracketFunction: true
+BreakBeforeCloseBracketIf: true
+PackArguments: {BinPack: OnePerLine}
+PackParameters: {BinPack: OnePerLine}
+AllowAllArgumentsOnNextLine: false

.coderabbit.yaml

@@ -65,7 +65,7 @@ reviews:
     custom_checks: []
 
   path_instructions:
-    - path: "cuda_bindings/**/*"
+    - path: "cuda_bindings_13/**/*"
       instructions: |
         Focus on Cython binding correctness, API and ABI stability, error-code propagation,
         resource ownership and reference counting, GIL handling, cross-platform behavior.
@@ -122,23 +122,23 @@ knowledge_base:
     filePatterns:
       - "AGENTS.md"
       - "CONTRIBUTING.md"
-      - "cuda_bindings/AGENTS.md"
+      - "cuda_bindings_13/AGENTS.md"
       - "cuda_core/AGENTS.md"
       - "cuda_core/tests/AGENTS.md"
       - "cuda_pathfinder/AGENTS.md"
       - "cuda_python/AGENTS.md"
       - "benchmarks/cuda_bindings/AGENTS.md"
       - "benchmarks/cuda_core/AGENTS.md"
-      - "cuda_bindings/README.md"
+      - "cuda_bindings_13/README.md"
       - "cuda_core/README.md"
       - "cuda_pathfinder/DESCRIPTION.rst"
       - "cuda_python/DESCRIPTION.rst"
-      - "cuda_bindings/docs/source/contribute.rst"
+      - "cuda_bindings_13/docs/source/contribute.rst"
       - "cuda_core/docs/source/contribute.rst"
       - "cuda_core/docs/source/concurrency.rst"
       - "cuda_core/docs/source/error_handling.rst"
       - "cuda_pathfinder/docs/source/contribute.rst"
-      - "cuda_bindings/docs/source/release.rst"
+      - "cuda_bindings_13/docs/source/release.rst"
       - "cuda_core/docs/source/release.rst"
       - "cuda_pathfinder/docs/source/release.rst"
       - "cuda_python/docs/source/release.rst"

.gitattributes

@@ -14,3 +14,11 @@ pixi.lock merge=binary linguist-language=YAML linguist-generated=true
 # `setuptools-scm` to correctly determine the version when building from a git
 # archive.  See #1609.
 .git_archival.txt export-subst
+
+# cuda.core compiles against the libcu++ headers of the vendored CCCL submodule
+# only; cuda_core/MANIFEST.in grafts those headers (and their licenses) into the
+# sdist explicitly.  setuptools-scm 10 lists the files of an initialized
+# submodule, which would otherwise add the entire CCCL tree to the sdist and
+# make every egg_info walk it.  "export-ignore" makes its file finder skip the
+# submodule.  See #2940.
+cuda_core/third_party/cccl export-ignore

.github/CODERABBIT.md

@@ -0,0 +1,34 @@
+<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. -->
+<!-- SPDX-License-Identifier: Apache-2.0 -->
+
+# CodeRabbit Configuration
+
+This document explains how CodeRabbit is configured for CUDA Python. For review
+commands and guidance, see the
+[CodeRabbit section of the contributing guide](../CONTRIBUTING.md#coderabbit).
+For complete product documentation, see the
+[CodeRabbit documentation](https://docs.coderabbit.ai/).
+
+CUDA Python configures CodeRabbit through [`.coderabbit.yaml`](../.coderabbit.yaml)
+in the repository root. For pull requests from a branch in the same repository,
+the configuration in that branch is used for the review. Pull requests from
+forks use the target branch's configuration instead, so changes to
+`.coderabbit.yaml` in a fork do not affect that review.
+
+When setting up or updating CodeRabbit:
+
+1. Keep repository-specific settings in `.coderabbit.yaml`.
+2. Use `@coderabbitai configuration` on a pull request to inspect the resolved
+   configuration. This is useful when checking whether CodeRabbit is using the
+   expected repository settings for that pull request.
+3. Use `@coderabbitai generate configuration` to export the resolved
+   configuration if a new baseline is needed. This is useful when moving
+   settings into a reviewable repository configuration file.
+4. Keep configuration changes small and reviewable.
+5. Use `reviews.path_instructions` for path-specific review guidance.
+6. Use `knowledge_base.code_guidelines.filePatterns` for CUDA Python guidance
+   files that CodeRabbit should read as review context.
+
+The CUDA Python configuration should keep comments focused on correctness, API
+stability, performance, security, and other high-impact issues. Avoid enabling
+features that add noisy generated comments or code by default.

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,13 +1,13 @@
 ## Description
 
-<!-- Every PR should have a corresponding issue that describes and motivates the work done in the PR -->
+<!-- Link the relevant issue, if any. -->
 closes <!-- Link issue here -->
 
 <!-- Provide a standalone description of changes in this PR. -->
 
 <!-- Note: The pull request title will be included in the CHANGELOG. -->
 
 ## Checklist
-<!-- TODO: - [ ] I am familiar with the [Contributing Guidelines](). -->
+- [ ] I have read the [Contributing Guidelines](https://github.com/NVIDIA/cuda-python/blob/main/CONTRIBUTING.md#coordinate-before-implementing).
 - [ ] New or existing tests cover these changes.
 - [ ] The documentation is up to date with these changes.

.github/RELEASE-core.md

@@ -6,9 +6,32 @@
 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)
+[CI: Release](workflows/release.yml)
 workflow.
 
+To release `cuda-pathfinder`, dispatch **CI: Release** with
+`component` set to `cuda-pathfinder`, `release-action` set
+to `full-release`, and `git-tag` set to the existing
+`cuda-pathfinder-v<VERSION>` tag. The workflow finds the successful
+tag-triggered CI run, checks release notes, creates or reuses a draft,
+builds and deploys versioned docs, and uploads the source archive, checksum,
+and wheels. It publishes to TestPyPI, verifies installation and the imported
+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 default `dry-run` action validates preparation, builds docs, and
+collects release artifacts without creating a GitHub Release or publishing
+packages. It can be dispatched from a development branch; use
+`dry-run-docs-branch` only when a preview deployment is needed.
+
 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

.github/actionlint.yaml

@@ -15,9 +15,35 @@ paths:
   ".github/workflows/build-docs.yml":
     ignore:
       - 'unexpected key "queue" for "concurrency" section'
+      # GitHub supports self-repository ($/) action references, but the latest
+      # actionlint release does not yet recognize them (rhysd/actionlint#711).
+      - 'specifying action "\$/[^"]+" in invalid format because ref is missing'
   ".github/workflows/cleanup-pr-previews.yml":
     ignore:
       - 'unexpected key "queue" for "concurrency" section'
   ".github/workflows/ci-workflow-health.yml":
     ignore:
       - 'unexpected key "queue" for "concurrency" section'
+  # GitHub supports self-repository ($/) action references, but the latest
+  # actionlint release does not yet recognize them (rhysd/actionlint#711).
+  ".github/workflows/release.yml":
+    ignore:
+      - 'specifying action "\$/[^"]+" in invalid format because ref is missing'
+  ".github/workflows/test-wheel-linux.yml":
+    ignore:
+      - 'specifying action "\$/[^"]+" in invalid format because ref is missing'
+  ".github/workflows/test-wheel-windows.yml":
+    ignore:
+      - 'specifying action "\$/[^"]+" in invalid format because ref is missing'
+  ".github/workflows/build-wheel.yml":
+    ignore:
+      - 'specifying action "\$/[^"]+" in invalid format because ref is missing'
+  ".github/workflows/pre-commit.yml":
+    ignore:
+      - 'specifying action "\$/[^"]+" in invalid format because ref is missing'
+  ".github/workflows/test-sdist-windows.yml":
+    ignore:
+      - 'specifying action "\$/[^"]+" in invalid format because ref is missing'
+  ".github/workflows/coverage.yml":
+    ignore:
+      - 'specifying action "\$/[^"]+" in invalid format because ref is missing'