Commit eb0899d
committed
Update binary build matrix for release 2.14
The 2.14 branch cut is done, so the test channel now serves 2.14.0 release
candidates. Applies the standard post-branch-cut update to `main`, matching
what `.github/workflows/release-pytorch-post-branch-cut.yml` does:
1. `CURRENT_CANDIDATE_VERSION` 2.13.0 -> 2.14.0 (= `CURRENT_NIGHTLY_VERSION`).
For the test channel `initialize_globals()` sets
`CURRENT_VERSION = CURRENT_CANDIDATE_VERSION`, surfaced as `stable_version`
and enforced by `smoke_test.py`. Left at 2.13.0 it fails with
`Torch version mismatch, expected 2.13.0 for channel test`.
2. Sync the test channel with nightly in `CUDA_ARCHES_DICT` (adds 13.4) and
`ROCM_ARCHES_DICT` (7.1, 7.2 -> 7.2, 7.14). These match what release/2.14
actually builds, so without them 2.14 RC validation would skip the cu134
and rocm7.14 wheels and try to validate rocm7.1 wheels that aren't
produced. `PYTHON_ARCHES_DICT` already matched nightly.
`CURRENT_STABLE_VERSION` stays 2.13.0 (current GA); it moves separately when
2.14 goes live. The release channel matrix is unchanged.
Test plan:
- `python -m tools.tests.test_generate_binary_build_matrix` - 11 tests pass.
- `--update-reference-files` produces no asset changes.
- Generated linux wheel matrix, before -> after:
- test: `stable_version` 2.13.0 -> 2.14.0, cuda +cu134, rocm 7.1 -> 7.14
- release: unchanged (2.13.0, cu126/130/132, rocm7.1/7.2)
- nightly: unchanged
Authored with the assistance of Claude Code.1 parent d607479 commit eb0899d
1 file changed
Lines changed: 3 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
45 | 45 | | |
46 | 46 | | |
47 | 47 | | |
48 | | - | |
| 48 | + | |
49 | 49 | | |
50 | 50 | | |
51 | 51 | | |
52 | 52 | | |
53 | 53 | | |
54 | | - | |
| 54 | + | |
55 | 55 | | |
56 | 56 | | |
57 | 57 | | |
| |||
99 | 99 | | |
100 | 100 | | |
101 | 101 | | |
102 | | - | |
| 102 | + | |
103 | 103 | | |
104 | 104 | | |
105 | 105 | | |
| |||
0 commit comments