build(deps): bump torch & torchvision from 2.8.0 to 2.9.0 in /requirements

[dependabot]

Bumps torch from 2.8.0 to 2.9.0.

Release notes

Sourced from torch's releases.

2.9 Release Notes

PyTorch 2.9.0 Release Notes

• Highlights
• Backwards Incompatible Changes
• Deprecations
• New Features
• Improvements
• Bug fixes
• Performance
• Documentation
• Developers
• Security

Highlights

For more details about these highlighted features, you can look at the release blogpost. Below are the full release notes for this release.

Backwards Incompatible Changes

... (truncated)

Commits

• 0fabc3b CUDA aarch64 12.6 and 12.8 builds fix triton constraints (#165022)
• 26e023a [MPS] Update OS version in error message (#164949)
• 6f12be2 CUDA 13.0 builds fix on Amazon Linux 2023 (#164893)
• 42f0c2c update the baseline data for the operator benchmark (#164789)
• b015422 fix cpp extension distributed warning spew (#164785)
• d4c4307 Fix docker build issue after 164575 (#164779)
• 3b57315 [ROCm] Increase binary build timeout to 5 hours (300 minutes) (#164770)
• c74f057 Pin conda version for Docker builds (#164579)
• fd36458 [Cherry-Pick] Work Around exposing statically linked libstdc++ CXX11 ABI stro...
• 2f6387e [CherrryPick][2.9] Cherry pick request for `Reapply "Make functionalization V...
• Additional commits viewable in compare view

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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

---

📚 Documentation preview 📚: https://pytorch-lightning--21300.org.readthedocs.build/en/21300/

.

[github-actions]

⛈️ Required checks status: Has failure 🔴

Warning
This job will need to be re-run to merge your PR. If you do not have write access to the repository, you can ask Lightning-AI/lai-frameworks to re-run it. If you push a new commit, all of CI will re-trigger.

Groups summary

🟢 pytorch_lightning: Tests workflow

Check ID	Status
pl-cpu-guardian	success	✅

These checks are required after the changes to requirements/fabric/base.txt, requirements/fabric/examples.txt, src/lightning/fabric/utilities/spike.py, requirements/pytorch/base.txt, requirements/pytorch/examples.txt.

🔴 pytorch_lightning: lit GPU

Check ID	Status
pytorch.yml / Lit Job (nvidia/cuda:12.1.1-runtime-ubuntu22.04, pytorch, 3.10)	success	✅
pytorch.yml / Lit Job (lightning, 3.12)	failure	❌
pytorch.yml / Lit Job (pytorch, 3.12)	failure	❌

These checks are required after the changes to requirements/pytorch/base.txt, requirements/pytorch/examples.txt, requirements/fabric/base.txt, requirements/fabric/examples.txt, src/lightning/fabric/utilities/spike.py.

🟢 Benchmarks

Check ID	Status
benchmark.yml / Lit Job (fabric)	success	✅
benchmark.yml / Lit Job (pytorch)	success	✅

These checks are required after the changes to requirements/fabric/base.txt, requirements/fabric/examples.txt, requirements/pytorch/base.txt, requirements/pytorch/examples.txt, src/lightning/fabric/utilities/spike.py.

🟢 fabric: Docs

Check ID	Status
docs-make (fabric, doctest)	success	✅
docs-make (fabric, html)	success	✅

These checks are required after the changes to src/lightning/fabric/utilities/spike.py, requirements/fabric/base.txt, requirements/fabric/examples.txt.

🟢 pytorch_lightning: Docs

Check ID	Status
docs-make (pytorch, doctest)	success	✅
docs-make (pytorch, html)	success	✅

These checks are required after the changes to requirements/pytorch/base.txt, requirements/pytorch/examples.txt.

🟢 lightning_fabric: CPU workflow

Check ID	Status
fabric-cpu-guardian	success	✅

These checks are required after the changes to requirements/fabric/base.txt, requirements/fabric/examples.txt, src/lightning/fabric/utilities/spike.py.

🔴 lightning_fabric: lit GPU

Check ID	Status
fabric.yml / Lit Job (nvidia/cuda:12.1.1-runtime-ubuntu22.04, fabric, 3.10)	success	✅
fabric.yml / Lit Job (fabric, 3.12)	failure	❌
fabric.yml / Lit Job (lightning, 3.12)	failure	❌

These checks are required after the changes to requirements/fabric/base.txt, requirements/fabric/examples.txt, src/lightning/fabric/utilities/spike.py.

🟢 mypy

Check ID	Status
mypy	success	✅

These checks are required after the changes to requirements/fabric/base.txt, requirements/fabric/examples.txt, requirements/pytorch/base.txt, requirements/pytorch/examples.txt, requirements/typing.txt, src/lightning/fabric/utilities/spike.py.

🟢 install

Check ID	Status
install-pkg-guardian	success	✅

These checks are required after the changes to src/lightning/fabric/utilities/spike.py, requirements/fabric/base.txt, requirements/fabric/examples.txt, requirements/pytorch/base.txt, requirements/pytorch/examples.txt, requirements/typing.txt.

---

Thank you for your contribution! 💜

Note
This comment is automatically generated and updates for 70 minutes every 180 seconds. If you have any other questions, contact carmocca for help.

[codecov]

Codecov Report

❌ Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 87%. Comparing base (7d0d0ad) to head (4e500b1).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff            @@
##           master   #21300    +/-   ##
========================================
- Coverage      87%      87%    -1%     
========================================
  Files         269      269            
  Lines       23707    23707            
========================================
- Hits        20682    20549   -133     
- Misses       3025     3158   +133