bump min dependencies anticipating next major release on 2025-11-01

[GaetandeCast]

I will need the return_as=generator option of joblib 1.3 for #31279 . According to the maintenance guide, this version should be an acceptable dependency for the next major release. I updated the _min_dependencies according to the script linked in the maintainers guide. However I get the following error when trying to update the lock files:

RuntimeError: Command exited with non-zero exit code. Exit code: 1 Command: conda-lock lock --mamba --kind explicit --platform linux-64 --file build_tools/azure/pylatest_conda_forge_mkl_linux-64_environment.yml --filename-template build_tools/azure/pylatest_conda_forge_mkl_linux-64_conda.lock stdout: stderr: Locking dependencies for ['linux-64']... INFO:conda_lock.conda_solver:linux-64 using specs ['python', 'numpy', 'blas * mkl', 'scipy', 'cython', 'joblib', 'threadpoolctl', 'matplotlib', 'pandas', 'pyamg', 'pytest', 'pytest-xdist', 'pillow', 'pip', 'ninja', 'meson-python', 'pytest-cov', 'coverage', 'ccache', 'pytorch', 'pytorch-cpu', 'polars', 'pyarrow', 'array-api-strict', 'scipy-doctest'] Failed to parse json, Expecting value: line 1 column 1 (char 0) Could not lock the environment for platform linux-64 Command: ['/home/gaeta/miniforge3/condabin/mamba', 'create', '--prefix', '/tmp/tmp1plne90a/prefix', '--dry-run', '--json', '--override-channels', '--channel', 'conda-forge', '--channel', 'file:///tmp/tmpohnhg00y', 'python', 'numpy', 'blas * mkl', 'scipy', 'cython', 'joblib', 'threadpoolctl', 'matplotlib', 'pandas', 'pyamg', 'pytest', 'pytest-xdist', 'pillow', 'pip', 'ninja', 'meson-python', 'pytest-cov', 'coverage', 'ccache', 'pytorch', 'pytorch-cpu', 'polars', 'pyarrow', 'array-api-strict', 'scipy-doctest'] 

Cc: @ogrisel @glemaitre

[github-actions]

✔️ Linting Passed

All linting checks passed. Your pull request is in excellent shape! ☀️

_{Generated for commit: 6901cef. Link to the linter CI: here}

[glemaitre]

I updated the lock files locally and push. I did not get the failures.

[jeremiedbb]

Thanks for the PR @GaetandeCast. However, I don't think that we should merge such a PR so soon after releasing 1.7. The reason is that there probably will bug-fix releases for 1.7 before 1.8 and it will kind of prevent us (or at least make it very difficult) to backport CI fixes and also add the risk that we use features that are not available in the min versions of 1.7 to fix bugs for e.g. 1.7.1.