Repository navigation
Enable nightly build to test 2.13 - #3929
Merged
Merged
Conversation
Branch-cut step for the 2.13 release (mirrors #3831 for 2.12): - Re-enable the push-on-main trigger for build-tutorials-nightly.yml. - Pin torch==2.13.0 from the test channel in .jenkins/build.sh (USE_NIGHTLY path + the commented reference line), and update the 2.12 -> 2.13 comment. .ci/docker/requirements.txt stays at 2.12 until the move-to-stable step.
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/tutorials/3929
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 34d8906 with merge base 3cdec7b ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
jathu
approved these changes
Jun 29, 2026
atalman
commented
Jun 29, 2026
atalman
added a commit
that referenced
this pull request
Aug 26, 2026
Branch-cut step to start testing the 2.14 release in tutorials, mirroring #3929 for 2.13. The push-on-main trigger in build-tutorials-nightly.yml is already enabled, so only the pin moves this time.
atalman
added a commit
that referenced
this pull request
Sep 2, 2026
## Summary Branch-cut step to start testing the **2.14** release in tutorials. Mirrors #3929 ("Enable nightly build to test 2.13"). - **`.jenkins/build.sh`**: pin `torch==2.14.0` (from the `test` channel, cu130) on the `USE_NIGHTLY` path and the commented reference line; update the `2.13 -> 2.14` comment. Unlike #3929, **no workflow change is needed**: the `push` on `main` trigger in `.github/workflows/build-tutorials-nightly.yml` is still enabled from the 2.13 cycle, so the nightly tutorials build already runs on `main` and will pick up the 2.14 RC binaries with this pin. `.ci/docker/requirements.txt` is intentionally left at `torch==2.13` — that gets bumped to 2.14 at the later "move to stable binaries" step, once 2.14 is released. ## Verification `torch==2.14.0+cu130` is published on the test channel, so the pin resolves: ``` https://download.pytorch.org/whl/test/cu130/torch/ torch-2.14.0+cu130-cp312-cp312-manylinux_2_28_x86_64.whl torch-2.14.0+cu130-cp312-cp312-manylinux_2_28_aarch64.whl ``` cu130 remains the right channel for 2.14: CUDA 13.0 is the stable CUDA version in the 2.14 release matrix. ## Release playbook reference (2.13 -> 2.14) | step | 2.13 | 2.14 | | --- | --- | --- | | enable nightly build to test the RC | #3929 | this PR | | move to stable binaries after release | (2.13 equivalent) | follow-up |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Branch-cut step to start testing the 2.13 release in tutorials. Mirrors #3831 ("Enable nightly build to test 2.12").
.github/workflows/build-tutorials-nightly.yml: re-enable thepushonmaintrigger so the nightly tutorials build runs against the 2.13 RC binaries..jenkins/build.sh: pintorch==2.13.0(from thetestchannel, cu130) on theUSE_NIGHTLYpath and the commented reference line; update the2.12 -> 2.13comment..ci/docker/requirements.txtis intentionally left attorch==2.12— that gets bumped to 2.13 at the later "move to stable binaries" step (the #3891 equivalent), once 2.13 is released.Release playbook reference (2.12 -> 2.13)
Test plan
bash -n .jenkins/build.shpasses.mainand installstorch==2.13.0fromhttps://download.pytorch.org/whl/test/cu130(2.13.0 test wheels are published).