-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Build tools: update latest
versions
#11350
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Yeah, I think it's fine to update them all in June. We are only one week away from it and we need to do the work, review, deploy, etc still. |
latest
versions
Please let me know if you need any details about this (this also ships with the mamba solver as the new backend for conda, making it almost as fast as mamba CLI). Blog post: https://conda.org/blog/2023-11-06-conda-23-10-0-release |
We are using
|
We reached our 6 months policy, so we proceed to update all the versions. Related: * readthedocs/readthedocs.org#11350
We reached our 6 months policy, so we proceed to update all the versions. Related: * readthedocs/readthedocs.org#11350
We reached our 6 months policy, so we proceed to update all the versions. Related: * readthedocs/readthedocs.org#11350
* Build: update all `build.tools` and add latest versions Matches readthedocs/readthedocs-docker-images#205 Closes #11350 * Build: add the version of miniconda in the `build.tools` option * Test: update latest version
What's the problem this feature will solve?
The version we have of miniconda (4.7) is quite old, I remember checking for this some time ago, and thinking that there weren't more versions available (5.x for example). Turns out that they changed their versioning scheme some time ago... Their versions now appear to be linked to a python version and the miniconda version (e.g
miniconda3-3.12-24.1.2.0
).Describe the solution you'd like
We are close to June, that's our 6 months policy update for all build tools, so we can maybe wait until that to update it. Or just do one exception, as our policy mentions.
Alternative solutions
Maybe find a way to manually upgrade miniconda for users that need it?
Additional context
We have one user not being able to build their docs, a probable cause is the version of miniconda. See numba/pixie#12.
The text was updated successfully, but these errors were encountered: