This repository holds a minimal installer for conda specific to conda-forge. It can be directly compared to Miniconda, with the added feature that conda-forge is the default channel.
Miniforge installers are available here: https://github.com/conda-forge/miniforge/releases
Latest installers with python 3.7 in the base environment #miniforge3
- linux-aarch64 (also called
arm64
) - linux-ppc64le (also called
POWER8/9
) - linux-x86_64 (also called
amd64
) - osx-x86_64
Latest installers with pypy3.6 in the base environment #miniforge-pypy3
Follow the aarch64 and ppc64le migration status here: https://conda-forge.org/status/
- Automatic build of constructor.
- Automatic upload of constructor results.
- Automatic testing of constructor.
- Integration with conda-forge's developer documentation.
- Integration with conda-forge's official site.
- Upstream to Anaconda ?
After construction on Travis, the installer is tested against a range of distribution that match the installer architecture ($ARCH
). For example when architecture is aarch64
, the constructed installer is tested against:
- Centos 7
- Debian Buster (10)
- Ubuntu 16.04
- Ubuntu 18.04
- Ubuntu 19.10
Installers are built and uploaded via Travis but if you want to construct your own Miniforge installer, here is how:
# Configuration
export ARCH=aarch64
export DOCKERIMAGE=condaforge/linux-anvil-aarch64
bash build_miniforge.sh
To release a new version of Miniforge:
- Open a new PR.
- Edit
Miniforge3/construct.yaml
.- Update the
version
tag to:$CONDA_VERSION-$BUILD_NUMBER
. For example,4.7.11-0
. - Update
conda
version in thespecs
section to$CONDA_VERSION
. - Update
python
version in thespecs
section to the Python version used in Miniconda.
- Update the
- Once CI is happy, merge into
master
. - Tag
HEAD
to$CONDA_VERSION-$BUILD_NUMBER
and push the tag:git tag $CONDA_VERSION-$BUILD_NUMBER
git push origin master --tags
Relevant conversations: