build(deps): update pandas requirement from <2.4.0,>2.0 to >2.0,<3.1.0 in /requirements

[dependabot]

Updates the requirements on pandas to permit the latest version.

Release notes

Sourced from pandas's releases.

pandas 3.0.0

We are pleased to announce the release of pandas 3.0.0, a major release from the pandas 2.x series. This release includes various new features, bug fixes, and performance improvements, as well as possible breaking changes.

The pandas 3.0 release removed a functionality that was deprecated in previous releases. It is recommended to first upgrade to pandas 2.3 and to ensure your code is working without warnings, before upgrading to pandas 3.0.

Highlights include:

• Dedicated string data type by default
• Consistent copy/view behaviour with Copy-on-Write (CoW) (a.k.a. getting rid of the SettingWithCopyWarning)
• New default resolution for datetime-like data
• Initial support for the new pd.col syntax

See the announcement blog post and the detailed release notes for a list of all the changes.

Pandas 3.0.0 supports Python 3.11 and higher. The release can be installed from PyPI

python -m pip install --upgrade pandas==3.0.*

Or from conda-forge

conda install -c conda-forge pandas=3.0

Please report any issues with the release on the pandas issue tracker.

Thanks to all the contributors who made this release possible.

Commits

• 366ccdf RLS: 3.0.0
• 139f4d0 DOC: split/reorder other enhancements section in 3.0.0 whatsnew notes (#63762)
• fd2a4f4 TST: assert reading of legacy pickles against current data (#61792)
• cc0bcaa DOC: update whatsnew section on datetimelike resolution (#63780)
• 3ddbb49 DOC: remove 2.3.4 whatsnew file from released 3.0 docs (#63779)
• ee63532 CLN: Create temporary HDF5 file path and HDFStore for pytables tests (#63492)
• 9512e99 CoW: better chained assignment warning message for update() method (#63500)
• 1db90d5 API: rename read_iceberg selected_fields keyword to columns (#63748)
• c9b51fa BUG: .str methods failing on PyArrow using regex with \Z (#63705)
• 7cff0f4 API: Period.to_timestamp default to microsecond unit (#63760)
• 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--21509.org.readthedocs.build/en/21509/

[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	failure	❌

These checks are required after the changes to requirements/pytorch/test.txt.

🟢 pytorch_lightning: lit GPU

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

These checks are required after the changes to requirements/pytorch/test.txt.

🟢 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/pytorch/test.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/test.txt.

🟢 mypy

Check ID	Status
mypy	success	✅

These checks are required after the changes to requirements/pytorch/test.txt.

🟢 install

Check ID	Status
install-pkg-guardian	success	✅

These checks are required after the changes to requirements/pytorch/test.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

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 79%. Comparing base (0c2025d) to head (cecda4c).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff            @@
##           master   #21509     +/-   ##
=========================================
+ Coverage      48%      79%    +31%     
=========================================
  Files         267      267             
  Lines       24015    24016      +1     
=========================================
+ Hits        11452    18960   +7508     
+ Misses      12563     5056   -7507