This keeps only the macos-14 jobs, which run on Apple Silicon M1, and removes the macos-13 jobs, which ran on x86-64. This relates to the commented discussion in #1944. There would also be the option of keeping some of them, but removing all of them decreases the workload the most while also being the simplest.
It also uses the label macos-latest instead, which is currently equivalent to macos-14.
Some information about the situation with macos-latest and the benefit of using it is presented in the second commit message.
That these jobs really are running on macOS 14, and more importantly that they are really running on ARM64, can be verified by examining the output of "Set up job" step. Here's an example.
Other operating systems' jobs continue to run on x86-64 machines (and none on ARM, yet). Only macOS jobs are removed.
This change leaves Python 3.7 without any macOS test job. That is probably okay, since it has been end-of-life for some time, and it remains tested on Ubuntu and Windows.
This keeps only the
macos-14jobs, which run on Apple Silicon M1, and removes themacos-13jobs, which ran on x86-64. This relates to the commented discussion in #1944. There would also be the option of keeping some of them, but removing all of them decreases the workload the most while also being the simplest.It also uses the label
macos-latestinstead, which is currently equivalent tomacos-14.macos-latestand the benefit of using it is presented in the second commit message.Other operating systems' jobs continue to run on x86-64 machines (and none on ARM, yet). Only macOS jobs are removed.
This change leaves Python 3.7 without any macOS test job. That is probably okay, since it has been end-of-life for some time, and it remains tested on Ubuntu and Windows.