chore(deps): consolidate Python dependency range widening

[MilesCranmerBot]

Consolidates multiple dependabot Python dependency bumps for the master branch.

Changes:

• juliacall >=0.9.28,<0.9.29 → >=0.9.28,<0.9.36
• ipykernel >=6,<7 → >=6,<8
• jax[cpu] >=0.4,<0.6 → >=0.4,<0.11
• pytest-cov >=5,<7 → >=5,<8

Closes #1031
Closes #1213
Closes #1214
Closes #1217
Closes #1139

[MilesCranmer]

@MilesCranmerBot I think you also have to adjust the versions in environment.yml? (And are there any other files to also update?)

[MilesCranmerBot]

Updated environment.yml to widen pyjuliacall from <0.9.29 → <0.9.36, matching pyproject.toml.

Checked all other files — no updates needed:

• setup.py is just a redirect (no deps)
• No requirements.txt
• CI workflows all pip install '.[dev]' (pull from pyproject.toml)

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[MilesCranmer]

@MilesCranmerBot It seems this one wasn't in sync with the just-merged backport PR to release-v1; could you please update this one with the backported compat ranges?

[MilesCranmerBot]

Synced this with the just-merged release-v1 backport ranges.

• Updated jax[cpu] in pyproject.toml from <0.7 to <0.11, matching chore(deps): consolidate Python dependency range widening for release-v1 #1240's final merged range.
• Updated the PR body to mention <0.11.
• Pushed commit: 419f38d (chore(deps): sync jax range with release-v1 backport)

Verification: pyproject.toml parses with tomllib and contains jax[cpu]>=0.4,<0.11. Full CI is running now; initial lightweight checks are passing/pending.

[MilesCranmer]

@MilesCranmerBot CI is failing

[MilesCranmerBot]

Root cause: all CI failures stem from the Julia Pkg server returning HTTP 404 for a registry hash (pkg.julialang.org/registry/.../9dda2732...). This is a transient upstream infrastructure issue, not caused by the dependency changes in this PR.

However, PySR's try_with_registry_fallback was too narrow — it only caught JuliaError with "Unsatisfiable requirements detected" messages. When the registry 404 occurs inside a juliapkg subprocess call, it surfaces as subprocess.CalledProcessError instead, so the eager registry fallback never triggered.

Fix pushed (11cddda): broadened the error detection to also recognize subprocess.CalledProcessError from juliapkg commands containing Pkg.Registry operations. Added a test case for this scenario.