November 2025 Releases

The November 2025 releases included updates to conda, conda-build, and conda-libmamba-solver! ๐ All of these have been released to both defaults and conda-forge channels.
This release includes preliminary support for fetching CEP 16 sharded repodata, a substantially more efficient way of distributing the necessary metadata to install packages in your environments. Read more about it in our sharded repodata blog post.
You can try it out by following these steps:
- Update to
conda-libmamba-solver25.11.0 or later - Enable it in your settings:
conda config --set plugins.use_sharded_repodata true - Set this environment variable:
CONDA_PLUGINS_USE_SHARDED_REPODATA=1
Note that sharded repodata requires that the target channels expose the necessary metadata, too, so it will only work with CEP-16-ready deployments. conda-libmamba-solver will fall back to non-sharded/monolithic repodata if not available, so you can mix sharded and non-sharded channels.
This feature is only available when using conda-libmamba-solver 25.11.0 and later and is not implemented in the classic solver.
Changes in conda 25.11.0โ
To update conda to the latest version, run:
conda install --name base conda=25.11.0
Notable Changes:
- Enhanced virtual packages plugin API with new fields for controlling override behavior.
- Added new
override_virtual_packages(alias:virtual_packages) configuration key to.condarcfor overriding virtual package versions and build numbers. - Added
createdandlast_modifiedproperties to conda environments. - Added new
envs_detailsfield toconda info --jsonoutput for inspecting properties of registered environments (also available viaconda info --envs --jsonandconda env list --json). - Fixed various bugs related to
MatchSpecserialization, channel URL handling, and Python 3.14 compatibility. - Improved warning for users attempting to add reserved environment variables like
PATHto environment configurations.
Check out the full changelog for more: 25.11.0
Changes in conda-build 25.11.0โ
To update conda-build to the latest version, run:
conda install --name base conda-build=25.11.0
Notable Changes:
- Added support for specifying a custom PyYAML loader when parsing configuration files via
conda_build.variants.parse_config_file. - Fixed
BUILDenvironment variable to properly respect thecdt_namevariant configuration. Previously, it was hardcoded to usecos6orcos7based on architecture. - Fixed Windows MSVC version detection for Python 3.5+.
- Updated CMake generator handling for CMake 4 compatibility (CMake 2 support was dropped in CMake 4).
- Python 3.9 support has been removed. The minimum supported Python version is now 3.10.
Check out the full changelog for more: 25.11.0
Changes in conda-libmamba-solver 25.11.0โ
To update conda-libmamba-solver to the latest version, run:
conda install --name base conda-libmamba-solver=25.11.0
Notable Changes:
- Added experimental support for CEP 16 sharded repodata (see announcement above).
- Added support for CEP 17
python_site_packages_path. - Fixed the
cpuonlymutex to correctly prevent CUDA packages from being installed, matching classic solver behavior. - Added new messaging for when
condais outdated, environment is frozen, andconda-selfis installed. - Python 3.9 support has been dropped. The minimum supported Python version is now 3.10.
- Added codspeed benchmarking GitHub action and benchmarks.
Check out the full changelog for more: 25.11.0
We โค๏ธ Our Communityโ
Altogether, we had 7 new contributors this release cycle; thank you to all of our open source community members for helping make these improvements possible.
- @danyeaw made their first contribution in conda#15208
- @lang-m made their first contribution in conda#13165
- @hoxbro made their first contribution in conda#15325
- @sumanth-manchala made their first contribution in conda#14179
- @shermansiu made their first contribution in conda-build#5800
- @agriyakhetarpal made their first contribution in conda-libmamba-solver#741
- @stacynoland made their first contribution in conda-libmamba-solver#766
