Repository navigation
cuda-core v1.1.0 release checklist #2291
Description
Tasks for cuda-core and cuda-bindings patch release
- File an internal nvbug to communicate test plan & release schedule with QA
- Ensure all pending PRs are reviewed, tested, and merged
- Check (or update if needed) the dependency requirements
- Finalize the doc update, including release notes ("Note: Touching docstrings/type annotations in code is OK during code freeze, apply your best judgement!")
- Update the docs for the new version
- Create a public release tag
- Wait for the tag-triggered CI run to complete, and use that run ID for release workflows
-
If any code change happens, rebuild the wheels from the new tag - Upload wheels to PyPI
- Finalize the announcement update on GitHub and publish the release (needed for conda)
- Update the conda recipe & release conda packages
- Post-release QA
- Send out the announcement internally
-
Send out the announcement externally (GitHub Release -> Announcement)
Activity
Andy-Jost commentedon Jul 6, 2026
Pending PRs on the
cuda.core v1.1.0milestoneSub-tracking for "Ensure all pending PRs are reviewed, tested, and merged". Rescanned 2026-07-08 against all open + merged items on the milestone.
Merged
__cuda_stream__(P1)Still open — to review, test, and merge
Moved off milestone
mdboom commentedon Jul 7, 2026
mdboom commentedon Jul 7, 2026
I don't think #2266 should be on this milestone. As currently written, it doesn't change cuda.core at all. There are plans to unify the examples better, but that's not going to happen before the 1.1.0 release, I don't think. Cc: @danielfrg for viz.
danielfrg commentedon Jul 7, 2026
yes, we dont need that for 1.1 - I moved it
Andy-Jost commentedon Jul 10, 2026
Tracking NVBUG for SWQA validation: https://nvbugspro.nvidia.com/bug/6421722
leofang commentedon Jul 11, 2026
Internal announcements were posted. Let's close this. Thanks to @Andy-Jost @jollylili and all for driving this release across the finish line! 🎉