[pull] main from pytorch:main by pull[bot] · Pull Request #433 · garymm/tutorials · GitHub
Skip to content

[pull] main from pytorch:main#433

Merged
pull[bot] merged 1 commit into
garymm:mainfrom
pytorch:main
Jun 29, 2026
Merged

[pull] main from pytorch:main#433
pull[bot] merged 1 commit into
garymm:mainfrom
pytorch:main

Conversation

@pull

@pull pull Bot commented Jun 29, 2026

Copy link
Copy Markdown

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

## 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 the
`push` on `main` trigger so the nightly tutorials build runs against the
2.13 RC binaries.
- **`.jenkins/build.sh`**: pin `torch==2.13.0` (from the `test` channel,
cu130) on the `USE_NIGHTLY` path and the commented reference line;
update the `2.12 -> 2.13` comment.

`.ci/docker/requirements.txt` is intentionally left at `torch==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)
| Step | 2.12 PR | 2.13 |
|------|---------|------|
| Enable nightly build to test the RC | #3831 | **this PR** |
| Move to stable binaries (requirements.txt) | #3891 | follow-up at
release |

## Test plan
- `bash -n .jenkins/build.sh` passes.
- After merge, the nightly tutorials build runs on `main` and installs
`torch==2.13.0` from `https://download.pytorch.org/whl/test/cu130`
(2.13.0 test wheels are published).
@pull pull Bot locked and limited conversation to collaborators Jun 29, 2026
@pull pull Bot added the ⤵️ pull label Jun 29, 2026
@pull pull Bot merged commit cb473bc into garymm:main Jun 29, 2026
1 of 2 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant