Skip to content

Commit 416c943

Browse files
committed
docs: align Core release checks with local bindings builds
1 parent 478b9be commit 416c943

1 file changed

Lines changed: 5 additions & 6 deletions

File tree

‎.github/RELEASE-core.md‎

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -91,16 +91,15 @@ The `cu12`/`cu13` extras declare the `cuda-bindings` floors. A release
9191
does not raise a floor to the newest `cuda-bindings`; see "Bumping the
9292
cuda-bindings floor" in `cuda_core/AGENTS.md`. Check the floors instead:
9393

94-
- The minor of each floor equals the minor of the toolkit pin of its
95-
major in `ci/versions.yml` (`build` for the current major, `prev_build`
96-
for the prior major). If a floor's minor is lower, the toolkit-bump
94+
- The minor of each floor equals the minor of that major's toolkit pin
95+
in `ci/versions.yml`. If a floor's minor is lower, the toolkit-bump
9796
window is open: move the floor before the release.
9897
- In the latest CI run on `main`, the CUDA 13 rows whose CUDA minor
99-
differs from the `build` pin (for example "CUDA 13.0.2") installed the
98+
differs from the current major's toolkit pin (for example "CUDA 13.0.2") installed the
10099
literal floor. Their logs show `Installing bindings (source: floor)` and
101100
`cuda-bindings==<floor>`, and no "predates ... headers" line. Standard
102-
CI does not install the CUDA 12 floor: its rows use the 12.9.x backport
103-
build.
101+
CI does not install the CUDA 12 floor: its rows use the same-run
102+
maintenance bindings build.
104103
- The release notes list every floor move since the last release.
105104

106105
Update the `cuda-core` pin in `cuda_python/setup.py` to the new minor

0 commit comments

Comments
 (0)