deps: bump torch upper cap to <2.13.0 (allow xpu 2.11.0 / 2.12.0)#658
Merged
Conversation
unsloth/pyproject.toml ships intel-gpu extras pinning torch-2.11.0+xpu and torch-2.12.0+xpu (added in unslothai/unsloth#5484), but unsloth_zoo's own torch constraint was capped at <2.11.0. The pip resolver consequently could not satisfy `pip install .[intel-gpu-torch2110]` or `.[intel-gpu-torch2120]` end-to-end: it either failed outright or fell back to a stale unsloth_zoo (2026.3.6) that does not enforce the cap. Relax the cap to <2.13.0 so torch 2.11.x and 2.12.x are admissible. Leaves torch>=2.4.0 floor intact and keeps the future-version cap as a safety net.
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
This was referenced May 17, 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
1 participant
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
Bumps the torch upper bound from
<2.11.0to<2.13.0in the base dependency block so that the newtorch-2.11.0+xpuandtorch-2.12.0+xpuintel-gpu extras in unsloth (added in unslothai/unsloth#5484) can actually resolve.Why
unsloth/pyproject.tomlnow ships:intel-gpu-torch2110-> pinstorch-2.11.0+xpuintel-gpu-torch2120-> pinstorch-2.12.0+xpuWithout this PR, pip rejects those extras because every recent
unsloth_zoorelease declarestorch>=2.4.0,<2.11.0in its own dependency block. The reporter on unslothai/unsloth#5494 hit this directly: their install of.[intelgputorch2120]fell back to a stale unsloth_zoo (2026.3.6) and they had to manually runuv pip install --upgrade --no-deps unsloth_zooto bypass the cap.What
A single character bump on the torch upper bound, leaves everything else untouched:
<2.13.0keeps a defensive cap on future torch versions while admitting the two new pinned versions we ship today.Test plan
After cutting a release that contains this change, the matching unsloth pyproject change (forthcoming follow-up to add
unsloth_zoo>=2026.X.Yfloor onhuggingfacenotorch) will pull this version throughpip install unsloth[intel-gpu-torch2120]and the resolver will picktorch==2.12.0+xpu+triton-xpu==3.7.1+ latest unsloth_zoo, instead of falling back to a stale unsloth_zoo as today.Closes part of unslothai/unsloth#5494 (the other half is the unsloth-side floor, which depends on a release containing this commit).