Skip to main content
Anaconda-supported software receives security fixes and updates as needed and appropriate. The methods of support and the associated SLA are tied to you as a person or organization and in alignment with your contract. By default, Anaconda supports only the most recent version of a product or feature when it is running on one of the currently supported Python versions, platforms, and CPU architectures. Anaconda recommends that you use the latest version of any product or feature to receive the latest security fixes and updates. There might be exceptions to the above for specific products or features, for certain contracts, or certain lifecycle stages. These are documented within the user documentation of the product or feature or in your contract.

​
Anaconda software lifecycle stages

​
Beta

Beta products are under active development and should not be used in production or sensitive environments. Beta products are not guaranteed to reach General Availability, and can instead go directly to End of Life. These are not covered by support contracts or SLAs.

​
End of Support (EOS)

When a product reaches End of Support, no new package versions, updates, or security fixes will be provided. This includes even the most recent versions. It will remain available for historical reference, and existing environments will continue to function. These packages do not receive updates and might contain known, unpatched vulnerabilities, so assess them against your own security requirements before use. There is not yet a migration plan to an alternative, nor an End of Life (EOL) date when it ceases to be available. Users are encouraged to leave feedback if they are using the product or feature to help inform the EOL process.

​
End of Life (EOL)

When a product reaches the End of Life, it will no longer receive security fixes or updates, including the most recent version. If the product or feature was Generally Available, there might be a suggested alternative to migrate to, and there will be a date indicating when it will no longer be available. If a product or feature never reached General Availability (for example, it was in Beta), it might be completely shut down and become unavailable without a migration path or advance notice date.

​
Archived

In some cases, something will be kept available for historic purposes in an archive. Things in the archive are End of Life and do not receive security fixes or updates. These should not be used in production or sensitive environments. These are not covered by support contracts or SLAs. These might be vulnerable or incompatible with modern systems.

​
Anaconda product and feature notes

​
Anaconda main channel

Anaconda’s supported Python versions, platforms, and CPU architectures for conda packages on the main channel are documented as linked. The supported versions are those that are supported at the time of the conda packages’ release. When conda packages contain open source software, Anaconda does not backport security fixes or updates. This means Anaconda will make a new version of the conda package available in alignment with the open source community version containing the patches and fixes.

​
Anaconda Distribution and Miniconda installers

Anaconda Distribution and Miniconda installers are point-in-time snapshots of a compatible set of packages tested to work together at the time of release. Installers are not rebuilt when individual packages receive security updates between releases. To receive the latest security fixes for packages included in an installer, users should update their base environment after installation. Anaconda publishes updated packages to the main channel on an ongoing basis. These updates are available immediately through conda regardless of which installer version was used.