{{ message }}
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.
jathu
approved these changes
Jun 29, 2026
atalman
commented
Jun 29, 2026
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).