https://pantsbuild.org/ logo
Join Slack
Powered by
The macos-10.15 runners hosted by GitHub are going...
# development
e
The macos-10.15 runners hosted by GitHub are going away:https://github.com/actions/virtual-environments/issues/5583 I'm prepping a PR to stop main CI bleeding. I already fixed this for Pex last night.
Its more impactful for Pants than Pex because of wheel building and potential backwards compatiility concerns with old Macs, but I don't see much else we can do except pay for another macstadium.
h
Hmmm this macOS 10.15 runner removal does have an impact on our users -- if they're using 10.15, they can't consume newer releases. That seems fine to me, given the timeline - not worth Pantsbuild spending money for macstadium
e
If someone wants to dig, a macosx10.15 XCode 11.7 SDK is installed on the macos-11 machines https://github.com/actions/virtual-environments/blob/macOS-11/20220724.1/images/macos/macos-11-Readme.md#installed-sdks with some effort and MACOSX_DEPLOYMENT_TARGET tricks? maybe you can get backwards compat. I wash my hands of the Mac at this level though since I don't have one, which would make figuring this all out way easier.
w
Maybe something like this (from one of my older Xcode CI builds)?
Copy code
jobs:
  build:
    runs-on: macos-11
    # Refer to Alamofire's CI for setting the XCode version (<https://github.com/Alamofire/Alamofire/blob/master/.github/workflows/ci.yml>)
    env:
      DEVELOPER_DIR: "/Applications/Xcode_13.2.1.app/Contents/Developer"

    steps:
      - uses: actions/checkout@v3
...
I got that from AlamoFire (https://github.com/Alamofire/Alamofire/blob/master/.github/workflows/ci.yml)
e
Definitely give it a spin @wide-midnight-78598 . What this needs is action.
h
If GitHub are phasing 10.15 out that seems like a good signal that we don't need to support it any more?
👍 1
But OTOH this seems like a bad way to make such decisions, because our hand was forced?
@wide-midnight-78598 will you have any cycles to look into this?
w
Probably not, as I've been dealing with a sick child all week, so a bit behind all around. Just for my understanding on this one - is this strictly a problem for macos users who are still running 10.15? Like, from 2019?
If so, I feel like there should be some sort of supported OS limit - 13 is coming out later this year, and some companies have been EOL'ing 10.15 this year (for example: https://support.box.com/hc/en-us/articles/4432599664403-Mac-OS-10-15-support-EOL-for-Desktop-Products) Edit: Even more: https://www.macworld.com/article/673697/what-version-of-macos-can-my-mac-run.html Assuming the developer has a machine from 2014+, they can run macOS 11 - so is this more of a CI breaking problem?
👍 1
h
Yeah, let's push the discussion up, but EOLing seems fine too
➕ 2
Open in Slack
PreviousNext
Powered by