Skip to content

ci: retire legacy branch-based bindings maintenance - #3322

Merged
rwgk merged 16 commits into
rwgk/cb12-staged-06-planningfrom
rwgk/cb12-staged-07-retirement
Nov 13, 2026
Merged

rwgk merged 16 commits into
rwgk/cb12-staged-06-planningfrom
rwgk/cb12-staged-07-retirement

Conversation

@rwgk

@rwgk rwgk commented Oct 31, 2026 •

Copy link
Copy Markdown
Contributor

— codex GPT-6 on behalf of Ralf —

Layer 7 of 7 of the staged "CUDA 12 bindings on main" stack. Previous: #3321. Stack map at the bottom.

What this PR does

Completes the migration to maintaining CUDA 12 and CUDA 13 bindings together on main. Routine CUDA 12 work moves to cuda_bindings_12/; the historical 12.9.x branch stays frozen except for emergency fixes reconciled into main.

  • Moves ci/versions.yml to schema 2: package roots with toolkit pins and current/maintenance release roles replace the old branch-based fields.
  • Deletes the obsolete backport.yml workflow and the 12.9.x Dependabot entry, and stops producing legacy wheel/test artifact aliases.
  • Adds a metadata consistency hook for both bindings roots’ SCM selectors, the metapackage selector table and Core’s bindings floors. Coverage selects the current root from the registry; Pixi pin checks cover both Core environments.
  • Requires CUDA_PYTHON_BUILD_MAJOR=12 or 13 for metapackage builds from a checkout or source archive. Standard setuptools-scm determines the version; a mismatched resolved major fails. Standalone sdists retain their fixed version and rebuild without a selector.
  • Consolidates maintenance guidance: checking applicable fixes in both roots, generation provenance and file seals, release routing, and moving to future CUDA majors.

Nightly rollout

Nightly reads configuration from the wheel artifacts’ source revision while using tooling from the workflow revision. It temporarily retains compatibility with pre-migration artifact sources. #3434 removes that route after this stack lands and a successful main CI run produces complete artifacts for both majors; the rollout is tracked in #3432. Compatibility with retained historical release tags remains separate.

Key files
Validation
  • At fbfd1445c78c: 404 CI-tool tests and all-files pre-commit passed locally, including explicit-major selection, dual-tag builds, standalone-sdist rebuilding and rejection of archive version mismatches.
  • Eight release rehearsals passed, covering CUDA 12/13 bindings and metapackages, Core, Pathfinder and retained CUDA 13 releases. These are earlier-revision evidence, not validation of the final rebased head.
  • Final landing validation is pending: full regular CI on #3322, then manual nightly using that run’s artifacts, plus all required per-PR checks. Relevant release validation will be repeated if conflict resolution changes release behavior.
Stack map: cumulative capabilities by layer
Layer PR Capability added
1 #3314 behaves exactly as before; CI has one reader for the two bindings roots; CUDA 13 versions can no longer match a v12.* tag
2 #3315 lets a developer build, test, and document cuda_bindings_12/; the PR-time CPU source-build smoke covers both roots; three CUDA 12 runtime fixes are in
3 #3317 builds the CUDA 12 bindings wheel itself and runs its GPU tests; cuda.core and the metapackage still consume 12.9.x artifacts
4 #3318 uses same-run CUDA 12 wheels everywhere; PR CI no longer reads the 12.9.x branch
5 #3319 can release CUDA 12 from a v12.9.N tag on main; CUDA 13 releases are unchanged
6 #3321 builds and tests only what a change needs, per bindings root, reusing baseline artifacts
7 #3322 adopts the schema-2 registry, removes backport automation, adds metadata checks and maintenance docs; 12.9.x is frozen

Layers #3314 and #3315 have merged. The remaining five migration PRs (#3317, #3318, #3319, #3321 and #3322) will land together using GitHub’s atomic stack merge, with full CI on #3322 as described in the landing plan. #3434 follows separately, after a successful post-migration main CI run supplies complete artifacts for both CUDA majors.

@copy-pr-bot

copy-pr-bot Bot commented Oct 31, 2026

Copy link
Copy Markdown
Contributor

Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

@rwgk
rwgk added this pull request to stack #3316 October 31, 2026 06:04
@github-actions github-actions Bot added CI/CD CI/CD infrastructure cuda.bindings Everything related to the cuda.bindings module cuda.core Everything related to the cuda.core module labels Oct 31, 2026
@rwgk rwgk added this to the cuda.bindings next milestone Oct 31, 2026
@rwgk rwgk added enhancement Any code-related improvements and removed cuda.core Everything related to the cuda.core module labels Oct 31, 2026
@rwgk rwgk self-assigned this Oct 31, 2026
@rwgk
rwgk force-pushed the rwgk/cb12-staged-07-retirement branch from c42bcf9 to 1c13b86 Compare October 31, 2026 07:49
@github-actions github-actions Bot added the cuda.core Everything related to the cuda.core module label Oct 31, 2026
@rwgk
rwgk force-pushed the rwgk/cb12-staged-07-retirement branch from 1c13b86 to e91c0cb Compare October 31, 2026 08:03

rwgk commented Oct 31, 2026

Copy link
Copy Markdown
Contributor Author

/ok to test e91c0cb

@mdboom mdboom left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only bookkeeping issue my agent pointed out is that the PR description is stale. But that doesn't need to hold up merging.

@rwgk

rwgk commented Nov 12, 2026

Copy link
Copy Markdown
Contributor Author

— codex GPT-6 on behalf of Ralf —

For landing this stack, I’ll add [no-ci] to the titles of #3317, #3318, #3319 and #3321, and run full CI on #3322.

GitHub’s native stack merge through #3322 is all-or-nothing, and main currently has no merge queue that could split the operation. This lets us validate the combined end state once, avoiding four additional full-CI runs. All required per-PR checks must still pass. #3434 remains a separate follow-up.

Before merging, we’ll:

  • Rebase onto current main and run full regular CI on ci: retire legacy branch-based bindings maintenance #3322, verifying coverage of both bindings majors and their consumers.
  • Manually run CI: Nightly optional-deps from the same stack revision, explicitly supplying that successful CI run’s ID so nightly tests the new artifacts.
  • Require both runs and the required per-PR checks to pass on the final revisions before merging the five PRs together.

The completed release rehearsals remain supporting evidence; we’ll repeat affected validation if conflict resolution changes release behavior.

After merging, we’ll verify that main produces complete artifacts for both majors before proceeding with #3434.

rwgk added 16 commits November 12, 2026 18:59
Signed-off-by: Ralf W. Grosse-Kunstleve <[email protected]>
Signed-off-by: Ralf W. Grosse-Kunstleve <[email protected]>
@rwgk
rwgk force-pushed the rwgk/cb12-staged-07-retirement branch from 59d5646 to 69317a8 Compare November 13, 2026 03:04
@rwgk

rwgk commented Nov 13, 2026

Copy link
Copy Markdown
Contributor Author

/ok to test 69317a8

@rwgk

rwgk commented Nov 13, 2026

Copy link
Copy Markdown
Contributor Author

— codex GPT-6 on behalf of Ralf —

The five migration PRs (#3317, #3318, #3319, #3321 and #3322) are rebased onto main at b7150783, approved, and ready to merge together through this PR. All required checks passed. One unassigned nightly test is accepted as a runner-capacity exception.

Pre-merge validation and the runner exception

Tested stack tip: 69317a881bcf.

PR PR CI
#3317 Passed
#3318 Passed
#3319 Passed
#3321 Passed
#3322 Passed

All five PR CI runs passed on their first attempt; no reruns were needed. The lower four retain [no-ci] as announced. The combined stack's full PR build/test matrix ran on #3322, with 105 successful jobs. The auxiliary security, pre-commit and source-build workflows also passed for all five PRs.

Local validation: 404 CI-tool tests passed at the stack tip, and all-files pre-commit passed in every migration layer. Rebase conflict resolutions were independently reviewed to preserve main's pinned GitHub CLI installer and Core test fixes.

Nightly validation used the same stack revision and explicitly selected the new PR CI artifacts. 39 jobs passed, with zero failures. The released-Core test on Windows A100/MCDM remains queued without a runner and has not run. After reviewing runner availability, we accepted this specific exception to the earlier requirement that both workflows finish green. The job remains queued; monitoring is stopped.

The previously completed release rehearsals remain earlier-revision evidence. They were not repeated for this rebase, whose incoming changes concerned GitHub CLI installation and Core tests.

#3434 remains a separate follow-up, gated on the first successful post-migration main CI run supplying complete artifacts for both CUDA majors.

@rwgk
rwgk merged commit 9a44af1 into main Nov 13, 2026
159 checks passed
@rwgk
rwgk deleted the rwgk/cb12-staged-07-retirement branch November 13, 2026 05:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI/CD CI/CD infrastructure cuda.bindings Everything related to the cuda.bindings module cuda.core Everything related to the cuda.core module enhancement Any code-related improvements

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants