Remove unjustified upper bounds on runtime dependency pins

[adrian-prior]

Summary

Removes the <Y upper bounds on torch, pandas, scikit-learn, scipy, and tabpfn in the runtime dependencies list. These caps were causing real-world breakage — most recently, tabpfn<7 silently pulled tabpfn 6.4.1 into fresh installs of tabpfn-extensions[all], which in turn made the Colab quickstart default to the v2.5 model instead of v2.6. See PRI-280 and the Slack discussion below.

The main tabpfn package doesn't cap these dependencies either, so this also just aligns our conventions.

What changed

 dependencies = [
-    "torch>=2.1,<3",
-    "pandas>=1.4.0,<3",
-    "scikit-learn>=1.6.0,<1.7",
-    "scipy>=1.11.1,<2",
-    "tabpfn>=6.0.5,<8",
+    "torch>=2.1",
+    "pandas>=1.4.0",
+    "scikit-learn>=1.6.0",
+    "scipy>=1.11.1",
+    "tabpfn>=6.0.5",
     "tabpfn-common-utils[telemetry-interactive]>=0.2.0",
 ]

What was kept

Upper bounds that have an accompanying comment explaining the constraint are preserved:

• setuptools>=67.0.0,<82 (in hpo and all extras) — comment links to the pkg_resources removal transition.
• ruff==0.8.6 (in the dev group) — must match .pre-commit-config.yaml.
• autogluon.tabular==1.4.0 — exact pin, not a cap; being replaced with >=1.5.0,<1.6 in Bump AutoGluon to 1.5 and route per-version to RealTabPFNv2/v25 classes #274.

Why now

Per Leo's approval in Slack in the thread about PRI-280:

"Yes would be great to remove!!"

Test plan

• CI green (all existing tests should continue to pass — we're loosening constraints, not tightening them)

🤖 Generated with Claude Code

[chatgpt-codex-connector]

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Credits must be used to enable repository wide code reviews.

[gemini-code-assist]

Code Review

This pull request removes the upper version constraints for several core dependencies in pyproject.toml, including torch, pandas, scikit-learn, scipy, and tabpfn. The review feedback suggests that simply removing the upper bound for tabpfn may still allow problematic versions to be installed; therefore, it is recommended to increase the minimum version requirement to 7.0.0 to ensure compatibility.

[alanprior]

I think the solution is to only change "tabpfn>=6.0.5". Were the other upper limits causing any issues? New majors DO TEND TO BREAK things.

cc @LeoGrin

[alanprior]

@adrian-prior WDYT?

[LeoGrin]

Thanks!! Checked and the CI is testing the latest version