Repository navigation
[CI] Build Python 3.10 release wheels against PyTorch 2.14 - #4706
Merged
Merged
Conversation
PyTorch 2.15 requires Python 3.11+, so the Python 3.10 wheel builds fail with 'No matching distribution found for torch==2.15.0' and block the release. - The wheel workflows take a python-versions input, defaulting to 3.11-3.14. - release.yml builds 3.11-3.14 against pytorch_release and adds one Python 3.10 job per platform against the new pytorch_release_py310 input (default release/2.14, torch 2.14.1). Builds stay sequential and Collect Wheels waits for all eight. - README: note the 3.10 wheels and use cu132 in the CUDA example, since the torch 2.15 matrix has no cu128 build.
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/rl/4706
Note: Links to docs will display an error until the docs builds have been completed. ⏳ No Failures, 3 PendingAs of commit e7fd5a4 with merge base 003c5f4 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
meta-cla
Bot
added
the
CLA Signed
github-actions
Bot
added
CI
theap06
marked this pull request as ready for review
November 8, 2026 03:32
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
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.
Description
PyTorch 2.15.0 requires Python 3.11+ and ships no cp310 wheels, so every Python 3.10 job in the v0.15.0 release dry run fails with
No matching distribution found for torch==2.15.0, and the release workflow only publishes when every build passes. This keeps Python 3.10 users on the latest TorchRL by building their wheels against PyTorch 2.14.1.build-wheels-*.ymlworkflows take apython-versionsinput, defaulting to 3.11 to 3.14. Push-triggered wheel builds no longer try 3.10.release.ymlbuilds 3.11 to 3.14 againstpytorch_releaseas before, and adds one Python 3.10 build job per platform against a newpytorch_release_py310input (defaultrelease/2.14, which pins torch 2.14.1 in test-infra and still lists Python 3.10). The builds stay sequential, and Collect Wheels waits for all eight.cu132in the CUDA wheel example, since the torch 2.15 matrix has no cu128 build.requires-pythonstays>=3.10and the wheels keeptorch>=2.11, so source builds on Python 3.10 with older torch keep working. PR CI does not run these workflows; they are validated by the v0.15.0 release dry run after merge.Motivation and Context
Unblocks the v0.15.0 release without dropping Python 3.10 users to 0.14.1.
Types of changes
Checklist