MACOSX_DEPLOYMENT_TARGET:  # [osx and x86]
  - '10.12'                # [osx and x86]

You should also add a run dependency on the respective OSX version:

  run:
    - __osx >={{ MACOSX_DEPLOYMENT_TARGET|default("10.9") }}  # [osx and x86_64]

The latter is also set automatically via a run_exports of the compiler('rust') package, but we add this line if you would increase the deployment target later in the feedstock for unrelated reasons.

Overall, this approach allows us to provide Python 3.12 for a wide range of packages already on the day of the offical Python 3.12 release. At the same time, we have stopped the Python 3.11 migration and added it to the list of default Python versions on conda-forge.

However, several core packages in the ecosystem now require at least 10.13 (or will very soon), in a way that we cannot be circumvent. These packages include libcxx, starting with version 17.0. This change will not affect already published artifacts, but in the near future, all new builds for OSX will require at least 10.13. This constraint will be implemented through the __osx virtual package, but the details of how we will achieve this are still being worked out. Only conda versions 4.8.0 or newer have this virtual package. If you are using a system with MacOS older than 10.13 and are using conda older than 4.8.0, you will need to either upgrade conda to at least 4.8.0 or upgrade your system to at least MacOS 10.13.

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.

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.

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).

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.

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.