increase minimum macOS deployment target to 10.13 by h-vetinari · Pull Request #5829 · conda-forge/conda-forge-pinning-feedstock (original) (raw)

This tiny change has been a long time coming, for a taste of the journey check out:

• META: {{ stdlib("c") }} migration conda-forge.github.io#2102
• DISCUSS: Raise MacOS minimum target from 10.9 to 10.13? conda-forge.github.io#1844

Closes conda-forge/conda-forge.github.io#1844

We've already announced the move last August, but needed a whole bunch of new functionality to make things work.

I proposed in the core call just now to do this separately for macOS (as we've promised to move to glibc 2.17 on linux in June, and this will probably be an even bigger change), so that we get to test it in real life, and also since all the prerequisites are there now.

In particular, feedstocks that haven't yet been touched by the stdlib-piggyback migrator (which will keep running; it adds the required {{ stdlib("c") }} to the recipes whenever a migrator or version bump comes by) will now get a linter warning to add it (as of conda-smithy 3.35), so that a warning-free feedstock will continue to produce correct artefacts. This was what had been agreed in the last core call, and people were fine to bump this in the core call just now as well.

Still, CC @conda-forge/core if anyone has input. Otherwise I'll merge this in ~48h.