Skip to content

Commit a109f42

Browse files
jaimergpbeckermrh-vetinari
committed
Bumping Minimum MacOS version to 10.13
#1993 Co-authored-by: Matthew R. Becker <[email protected]> Co-authored-by: h-vetinari <[email protected]>
1 parent d5f7060 commit a109f42

File tree

1 file changed

+22
-0
lines changed

1 file changed

+22
-0
lines changed
Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
# Bumping Minimum MacOS version to 10.13
2+
3+
We will bump the minimum MacOS version from 10.9 (released in Oct. 2013,
4+
end-of-life since Dec. 2016) to 10.13 (released Sept. 2017, end-of-life
5+
since Dec. 2020). The main reason we managed to support 10.9 this long
6+
at all, is that conda-forge is able to ship an up-to-date C++ standard
7+
library for OSX, `libcxx`, superseding the old one present in the MacOS
8+
SDK on the system (at least from the point-of-view of the respective
9+
conda environments).
10+
11+
However, several core packages in the ecosystem now require at least
12+
10.13 (or will very soon), in a way that we cannot be circumvent. These
13+
packages include `libcxx`,
14+
[starting](https://discourse.llvm.org/t/libc-bumping-minimal-deployment-target-for-building-the-dylib-static-library-on-macos/68912)
15+
with version 17.0. This change will not affect already published
16+
artifacts, but in the near future, all new builds for OSX will require
17+
at least 10.13. This constraint will be implemented through the `__osx`
18+
virtual package, but the details of how we will achieve this are still
19+
being worked out. Only `conda` versions 4.8.0 or newer have this virtual
20+
package. If you are using a system with MacOS older than 10.13 and are
21+
using `conda` older than 4.8.0, you will need to either upgrade `conda`
22+
to at least 4.8.0 or upgrade your system to at least MacOS 10.13.

0 commit comments

Comments
 (0)