Skip to main content

A GitHub action now monitors comments on issues in staged-recipes and will add language and review labels to issues/PRs when a staged-recipes sub-team is mentioned in a comment. It adds the Awaiting author contribution label if a member of staged-recipes removes the review-requested label. Unlike notifications, which are only sent to the users which are members of a team at the time of the mention, labels are persistent and visible to everyone, so they should be very helpful for identifying old PRs that need attention.

Due to technical issues in generating new feedstocks, we have deprecated using CircleCI and Drone.io for builds of new feedstocks. Existing CircleCI builds, if any, should be moved to azure. Existing Drone.io builds can be moved to Travis CI or cross-compiled/emulated builds on azure.

We have begun rolling out packages built for PyPy3.8 and PyPy3.9. This work may take a few weeks. See pypy in the user docs for information on how to set up a PyPy environment. Please report issues to the PyPy developers at https://foss.heptapod.net/pypy/pypy. We are also dropping PyPy3.7 in each feedstock as the newer versions of PyPy are added. New versions of migrated feedstocks will not be built for PyPy3.7 and that version of the python interpreter will not be receiving updates. As usual, you can track the status of the migration on our status page.

Due to changes in how Travis CI tracks open-source build time, we are deprecating using it for the win_*, osx_*, and linux_64 platforms.

Travis CI will be available only for platforms in their partner queues. These platforms currently include ppc64le, aarch64 and s390x.

Rerendering will raise an error if Travis CI is used for a non-partner queue platform in the conda-forge GitHub organization.

We will be migrating the default branches of all feedstocks and other conda-forge repos from master to main. We do expect some minor hiccups while this migration is going on. You will need to change to the main branch from master on any local clones via the following git commands:

git branch -m master main
git fetch origin
git branch -u origin/main main
git remote set-head origin -a

If you encounter any problems, please comment on this Github issue.

We are moving all conda-forge linux-64 jobs to use CentOS 7-based docker images. This will help users avoid conda/mamba solver errors where dependencies that need CentOS 7 cannot be installed. Importantly, our compiler stack will still default to using a CentOS 6 sysroot unless the recipe explicitly lists the CentoOS 7 sysroot package. This build configuration means that our core system ABI on linux will remain largely CentOS 6-compatible, keeping support for older systems largely intact. We will reconsider moving the default ABI to CentOS 7 at a later date.

The cloud.drone.io service we use for aarch64 builds is no longer accepting our API requests for triggering builds. We have been in contact with them, but have been unable to resolve the issue. Going forward, we will still be adding feedstocks to cloud.drone.io but we have moved all aarch64 builds to emulated builds on Azure. Cross-compilers are available as well for resource-intensive builds. Please rerender your feedstock as needed to get the updated configuration.

These compilers will become the default for building packages in conda-forge. One notable change in gcc 10 is that the -fopenmp`` flag in FFLAGSis dropped. In clang 12,-std=c++14explicit flag has been dropped fromCXXFLAGS, as it is the default compilation mode for clang 12. In gcc 11, the default is -std=gnu++17`. In clang>=12 and gcc>=11, we will not provide an explicit C++ standard, and will defer to the compiler default.