This was merged but as discussed on the PR [1] we probably want to
maintain the macOS deployment target to 12 to have wheels available
for pyarrow at least on 18.0.0.

I've created [2] to do that.

Thanks,
Raúl


[1] https://github.com/apache/arrow/pull/44212#discussion_r1785712757
[2] https://github.com/apache/arrow/issues/44314

El mar, 24 sept 2024 a las 2:18, Sutou Kouhei (<k...@clear-code.com>) escribió:
>
> Hi,
>
> Thanks for sharing the information.
>
> We don't have macOS 11 + arm64 CI job for now. Removing
> macOS 12 + x86_64 CI jobs should not affect it.
>
> Other macOS patterns are:
> * macOS 13.4 + arm64 (release-macos-arm64)
> * macOS 13.3.1 + x86_64 (release-macos-x86_64)
> * macOS 13.3 + x86_64 (oldrel-macos-x86_64)
>
> Removing macOS 12 + x86_64 CI jobs from our CI jobs should
> not affect them too.
>
>
> Thanks,
> --
> kou
>
> In <cae+qdjytrjy8gunuibfnsopt46ew_qivuuqbiy4agg0drqr...@mail.gmail.com>
>   "Re: [C++] Can we drop support for macOS 12?" on Mon, 23 Sep 2024 19:10:20 
> -0500,
>   Jonathan Keane <jke...@gmail.com> wrote:
>
> > One place we will need to support some older macOSes is CRAN. Currently
> > their oldrel macos arm64 runner runs 11.6.7:
> > https://cran.r-project.org/web/checks/check_flavors.html#r-oldrel-macos-x86_64
> > we have generally not had problems with this in the past, even without
> > dedicated CI runners for it, but something to note.
> >
> > -Jon
> >
> >
> > On Mon, Sep 23, 2024 at 7:01 PM Sutou Kouhei <k...@clear-code.com> wrote:
> >
> >> Hi,
> >>
> >> Can we drop support for macOS 12?
> >> Related issue: https://github.com/apache/arrow/issues/44206
> >>
> >> Homebrew dropped support for macOS 12:
> >> https://github.com/Homebrew/brew/pull/18314
> >>
> >> GitHub Actions's macos-12 runner will be fully retired by
> >> the December 3rd, 2024:
> >>
> >> https://github.blog/changelog/2024-08-19-notice-of-upcoming-deprecations-and-breaking-changes-in-github-actions-runners/
> >>
> >> It's difficult for us without them. Can we drop support for
> >> macOS 12?
> >>
> >>
> >> Thanks,
> >> --
> >> kou
> >>

Reply via email to