Micromamba is now deprecated as of July 2025 #369
Description
Your name
Bob Yantosca
Your affiliation
Harvard + GCST
What happened? What did you expect to happen?
As described at https://github.com/conda-forge/miniforge/blob/main/README.md, the Mambaforge installer (which also includes MicroMamba) is deprecated:
Update for July 2024:
As of July 2024, Mambaforge is deprecated. We suggest users switch to
Miniforge3 immediately. These installers will be retired from new releases
after January 2025. To assist in the migration, we will be introducing rollowing
brownouts to the latest Mambaforge installer. Installers up to version 24.5.0-1
will not have any brownouts. 24.5.0-1 will include a warning message.
Installers 2024.5.0-2 and later will have the following brownout schedule:
- The installer will refuse to proceed every two weeks in October
- The installer will refuse to proceed every ten days in November
- The installer will refuse to proceed every five days in December
- The installer will refuse to proceed in 2025+
Previous information:
With the release of
Miniforge3-23.3.1-0, that incorporated the changes in
#277, the packages and
configuration of Mambaforge and Miniforge3 are now identical. The
only difference between the two is the name of the installer and, subsequently,
the default installation directory.
We recommend switching to Miniforge3 immediately. These installers will be
retired in January 2025. To assist in the migration to Miniforge3 for CI users, we've stopped
the latest Mambaforge (24.5+) installer from proceeding with following schedule
- Every two weeks in October
- Every ten days in November
- Every five days in December
- Never in 2025
You can still find the latest installers in the 24.9.2 release.
What are the steps to reproduce the bug?
Installing Mamba as described in our documentation may lead to an error such as this:
Please attach any relevant configuration and log files.
No response
What GCPy version were you using?
1.6.3
What environment were you running GCPy on?
Personal computer
What python environment were you using?
See: https://github.com/geoschem/gcpy/blob/main/docs/environment_files/gcpy_environment_py312.yml
Will you be addressing this bug yourself?
Yes
Additional information
We will update the documentation at gcpy.readthedocs.io accordingly for the next GCPy release.