As you may be aware, we have delayed the deprecation of our CentOS 6 build system the linux64 platform several times. We have now set a formal deprecation date to be June 30, 2024. This date matches the end of extended life-cycle support from RedHat for RHEL 6. After this date, we build packages against CentOS 7 by default for linux64.

We have made the conda-forge Google Group read-only. Please use the new conda-forge discourse forum, our Gitter room, or it's Matrix/Element counterpart instead.

We have moved the CI job that makes new feedstocks to our conda-forge/admin-requests repo. The new location is reflected in the various links on repos and our status page.

conda-forge is moving to producing conda artifacts in the version 2 package format (also known as .conda). These artifacts allow for more efficient indexing and maintenance of the ecosystem. Our admin migrations bot will begin making PRs to feedstocks to change them over to the new artifact format. You will need conda version 4.7 or later to use the new .conda artifacts. Please leave a comment on this issue if you encounter problems or have feedback.

The CPython versions 3.8.14, 3.9.14, and 3.10.7 were released some weeks ago to mitigate CVE-2020-10735. The chosen mitigation strategy might cause errors (e.g. ValueError: Exceeds the limit (4300) for integer string conversion) in some libraries. If you are affected, please read the announcement and learn about the available workarounds in the CPython documentation.

The conda-forge team has decided to build and publish these releases with no additional changes. The new packages will be made available on or after 2022-11-10, following Anaconda's decision.

Conda is moving to CalVer per CEP 8. The first CalVer and last SemVer should be 22.9.0 and 4.14.0 respectively. This change maintains version order so you should not expect any issues.

Conda-Forge has been providing support for Python 3.7 for 4 years now.

Increasingly projects are moving off it (particularly in the PyData community). With Python 3.11's release coming around the corner (October 3rd), conda-forge plans to drop Python 3.7 support when Python 3.11 comes out. This will lighten the load on conda-forge infrastructure and make room for the new versions the community would like to support.

More details can be found in issue conda-forge-pinning-feedstock#2623. Feedback is welcome there.

Conda-forge has supported PyPy since almost 2.5 years now, and the initial PyPy 3.7 builds have been superseded in almost all aspects by the newer builds for 3.8 & 3.9. We are therefore dropping PyPy 3.7 as a supported python version, and will keep focusing on the more contemporary PyPy builds.

Microsoft has deprecated the Visual Studio (VS) 2017 compiler and removed it from all the CI they control (notably Azure Pipelines & Github Actions). This means that the default toolchain (== C/C++ compiler, linker, standard libraries, and related utilities) of that VS version - vc141 - is getting less and less use in upstream libraries (because public hosted CI doesn't use it anymore by default), and therefore support for it is bitrotting at an accelerating pace. We are therefore planning to move our toolchain on windows to vc142 (the default in VS2019) in two weeks, on 2022-08-25.

This will not affect you as a general user of conda-forge packages on windows; the only impact is that if you are locally compiling against artefacts produced by conda-forge and are still using VS2017 yourself, you will need to upgrade your compiler (VS2019 is a drop-in replacement & ABI-compatible).

Azure is removing their OSX 10.15 VM image and so we are bumping to 11. You will need to rerender your feedstock to get this change. Feedstocks without the new VM image specified will not build after Azure fully removes the old image. Please get in touch with us if you have issues or questions!