build: update torch requirement from <2.9.0,>=2.7.0 to >=2.7.0,<2.13.0#664
build: update torch requirement from <2.9.0,>=2.7.0 to >=2.7.0,<2.13.0#664dependabot[bot] wants to merge 1 commit into
Conversation
Updates the requirements on [torch](https://github.com/pytorch/pytorch) to permit the latest version. - [Release notes](https://github.com/pytorch/pytorch/releases) - [Changelog](https://github.com/pytorch/pytorch/blob/main/RELEASE.md) - [Commits](https://github.com/pytorch/pytorch/commits/v2.12.0) --- updated-dependencies: - dependency-name: torch dependency-version: 2.12.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit dcb0f01. Configure here.
| intel = [ | ||
| "intel-extension-for-pytorch>=2.7.0", | ||
| "torch>=2.7.0,<2.9.0", | ||
| "torch>=2.7.0,<2.13.0", |
There was a problem hiding this comment.
Widened torch range inconsistent with torchvision upper bound
Medium Severity
The torch upper bound in the intel extra was widened to <2.13.0 but the companion torchvision>=0.22.0,<0.24.0 constraint was not updated. Torchvision versions are tightly coupled with torch (e.g., torch 2.9→torchvision 0.24, torch 2.10→0.25, torch 2.12→~0.27), so the torchvision cap at <0.24.0 effectively still limits torch to ~2.8.x. Additionally, intel-extension-for-pytorch reached EOL at version 2.8 and will never support torch ≥2.9. The widened torch range is misleading and could cause resolver conflicts or confusing installation errors.
Reviewed by Cursor Bugbot for commit dcb0f01. Configure here.
Updates the requirements on torch to permit the latest version.
Release notes
Sourced from torch's releases.
... (truncated)
Changelog
Sourced from torch's changelog.
... (truncated)
Commits
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)