[PATCH] github-ci: update macos jobs to macos-15

[PATCH] github-ci: update macos jobs to macos-15

[Junio C Hamano]

GitHub from <no-reply@github.com> address keeps sending

  Subject: [Action Required] macOS 14 hosted runner image is closing down

and suggests to update to either macos-latest (macos-26) or
macos-15.  As we do not have strong reason to pick one over the
other, this patch picks more conservative choice with hopefully
smaller impact.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
 * Not tested at all and I do not do macos myself.

 .github/workflows/main.yml | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git i/.github/workflows/main.yml w/.github/workflows/main.yml
index b229739be8..d69f6f2b10 100644
--- i/.github/workflows/main.yml
+++ w/.github/workflows/main.yml
@@ -349,16 +349,16 @@ jobs:
         vector:
           - jobname: osx-clang
             cc: clang
-            pool: macos-14
+            pool: macos-15
           - jobname: osx-reftable
             cc: clang
-            pool: macos-14
+            pool: macos-15
           - jobname: osx-gcc
             cc: gcc-13
-            pool: macos-14
+            pool: macos-15
           - jobname: osx-meson
             cc: clang
-            pool: macos-14
+            pool: macos-15
     env:
       CC: ${{matrix.vector.cc}}
       CC_PACKAGE: ${{matrix.vector.cc_package}}

Re: [PATCH] github-ci: update macos jobs to macos-15

[brian m. carlson]

[-- Attachment #1: Type: text/plain, Size: 909 bytes --]

On 2026-10-16 at 22:46:36, Junio C Hamano wrote:
> GitHub from <no-reply@github.com> address keeps sending
> 
>   Subject: [Action Required] macOS 14 hosted runner image is closing down
> 
> and suggests to update to either macos-latest (macos-26) or
> macos-15.  As we do not have strong reason to pick one over the
> other, this patch picks more conservative choice with hopefully
> smaller impact.
> 
> Signed-off-by: Junio C Hamano <gitster@pobox.com>
> ---
>  * Not tested at all and I do not do macos myself.

I think this is fine if it passes CI.  There's not that much of a
difference in terms of POSIX-related functionality in different versions
of macOS, so upgrading to macOS 15 shouldn't be a problem.  I think 15
is a better option than 26 because we're more likely to avoid anything
new that older versions don't have.
-- 
brian m. carlson (they/them)
Toronto, Ontario, CA

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 325 bytes --]

Re: [PATCH] github-ci: update macos jobs to macos-15

[Patrick Steinhardt]

On Fri, Oct 16, 2026 at 03:46:36PM -0700, Junio C Hamano wrote:
> diff --git i/.github/workflows/main.yml w/.github/workflows/main.yml
> index b229739be8..d69f6f2b10 100644
> --- i/.github/workflows/main.yml
> +++ w/.github/workflows/main.yml
> @@ -349,16 +349,16 @@ jobs:
>          vector:
>            - jobname: osx-clang
>              cc: clang
> -            pool: macos-14
> +            pool: macos-15
>            - jobname: osx-reftable
>              cc: clang
> -            pool: macos-14
> +            pool: macos-15
>            - jobname: osx-gcc
>              cc: gcc-13
> -            pool: macos-14
> +            pool: macos-15
>            - jobname: osx-meson
>              cc: clang
> -            pool: macos-14
> +            pool: macos-15

Do we maybe want to update those jobs to use a mixture of macos-15 and
macos-26? In GitLab CI we use macos-15 for osx-clang and macos-26 for
everything else. Like that we have higher test coverage compared to only
exercising one major release.

Patrick

Re: [PATCH] github-ci: update macos jobs to macos-15

[Junio C Hamano]

Patrick Steinhardt <ps@pks.im> writes:

>>            - jobname: osx-meson
>>              cc: clang
>> -            pool: macos-14
>> +            pool: macos-15
>
> Do we maybe want to update those jobs to use a mixture of macos-15 and
> macos-26? In GitLab CI we use macos-15 for osx-clang and macos-26 for
> everything else. Like that we have higher test coverage compared to only
> exercising one major release.

I do not care too deeply, but variety is better than monoculture.
Let me roll a die and send v2 ;-)

Thanks.

[PATCH v2] github-ci: update macos jobs to macos-15

[Junio C Hamano]

GitHub from <no-reply@github.com> address keeps sending

  Subject: [Action Required] macOS 14 hosted runner image is closing down

and suggests to update to either macos-latest (macos-26) or
macos-15.  Use macos-15 for two of the four osx-* jobs, and
macos-26 for the other two jobs.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
 .github/workflows/main.yml | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml
index cf341d74db..e8f744d069 100644
--- a/.github/workflows/main.yml
+++ b/.github/workflows/main.yml
@@ -323,16 +323,16 @@ jobs:
         vector:
           - jobname: osx-clang
             cc: clang
-            pool: macos-14
+            pool: macos-15
           - jobname: osx-reftable
             cc: clang
-            pool: macos-14
+            pool: macos-26
           - jobname: osx-gcc
             cc: gcc-13
-            pool: macos-14
+            pool: macos-26
           - jobname: osx-meson
             cc: clang
-            pool: macos-14
+            pool: macos-15
     env:
       CC: ${{matrix.vector.cc}}
       CC_PACKAGE: ${{matrix.vector.cc_package}}

Range-diff against v1:
1:  c7124011e9 ! 1:  7ca9f53bab github-ci: update macos jobs to macos-15
    @@ Commit message
           Subject: [Action Required] macOS 14 hosted runner image is closing down
     
         and suggests to update to either macos-latest (macos-26) or
    -    macos-15.  As we do not have strong reason to pick one over the
    -    other, this patch picks more conservative choice with hopefully
    -    smaller impact.
    +    macos-15.  Use macos-15 for two of the four osx-* jobs, and
    +    macos-26 for the other two jobs.
     
         Signed-off-by: Junio C Hamano <gitster@pobox.com>
     
    @@ .github/workflows/main.yml: jobs:
                - jobname: osx-reftable
                  cc: clang
     -            pool: macos-14
    -+            pool: macos-15
    ++            pool: macos-26
                - jobname: osx-gcc
                  cc: gcc-13
     -            pool: macos-14
    -+            pool: macos-15
    ++            pool: macos-26
                - jobname: osx-meson
                  cc: clang
     -            pool: macos-14
-- 
2.56.0-314-g110ce7813b

Re: [PATCH v2] github-ci: update macos jobs to macos-15

[Todd Zullinger]

Junio C Hamano wrote:
> GitHub from <no-reply@github.com> address keeps sending
> 
>   Subject: [Action Required] macOS 14 hosted runner image is closing down
> 
> and suggests to update to either macos-latest (macos-26) or
> macos-15.  Use macos-15 for two of the four osx-* jobs, and
> macos-26 for the other two jobs.

I know very, very little about macOS (in general and with
respect to Github CI)...

Is it worth using `macos-latest` instead of `macos-26` and
letting those jobs move along with the current macOS runner
as it changes?

The documentation¹ links `macos-latest` to `macos-26` at the
moment, AFAICT.

I don't know if that moves to the next release too quickly
to be useful to Git or not.  If not, maybe using that will
be a more convenient way to get macOS coverage where we
don't have a strong preference for the version?

¹ https://docs.github.com/en/actions/reference/runners/github-hosted-runners#standard-github-hosted-runners-for-public-repositories

-- 
Todd

Re: [PATCH v2] github-ci: update macos jobs to macos-15

[brian m. carlson]

[-- Attachment #1: Type: text/plain, Size: 1497 bytes --]

On 2026-10-19 at 23:47:24, Todd Zullinger wrote:
> I know very, very little about macOS (in general and with
> respect to Github CI)...
> 
> Is it worth using `macos-latest` instead of `macos-26` and
> letting those jobs move along with the current macOS runner
> as it changes?
> 
> The documentation¹ links `macos-latest` to `macos-26` at the
> moment, AFAICT.
> 
> I don't know if that moves to the next release too quickly
> to be useful to Git or not.  If not, maybe using that will
> be a more convenient way to get macOS coverage where we
> don't have a strong preference for the version?

I believe macOS releases once a year, so I expect that the macOS version
for GitHub Actions will update about once a year as well and that one
version a year will be removed.

Using `macos-latest` would be the easiest way to keep up to date, but it
would also mean that we wouldn't test older OS features.  As far as
POSIX features, it's likely that macOS will stick pretty closely to the
standard because until very recently, it was UNIX certified, so that may
not be a practical concern.

I don't have a very strong opinion about what we should do one way or
the other.  I would be much more likely to want to test across different
versions of Linux, its C libraries, and compilers because there's much
more divergence there in terms of potentially breaking changes and a
much longer lifespan of OS versions.
-- 
brian m. carlson (they/them)
Toronto, Ontario, CA

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 325 bytes --]

Re: [PATCH v2] github-ci: update macos jobs to macos-15

[Todd Zullinger]

brian m. carlson wrote:
> On 2026-10-19 at 23:47:24, Todd Zullinger wrote:
>> Is it worth using `macos-latest` instead of `macos-26` and
>> letting those jobs move along with the current macOS runner
>> as it changes?
[...]
>> I don't know if that moves to the next release too quickly
>> to be useful to Git or not.  If not, maybe using that will
>> be a more convenient way to get macOS coverage where we
>> don't have a strong preference for the version?
> 
> I believe macOS releases once a year, so I expect that the macOS version
> for GitHub Actions will update about once a year as well and that one
> version a year will be removed.
> 
> Using `macos-latest` would be the easiest way to keep up to date, but it
> would also mean that we wouldn't test older OS features.

That's where the macos-15 jobs take effect.  To be sure, I
wasn't suggesting setting all of them to latest, just those
which are set to macos-26 here, as a way to get rolling
testing on macOS.

-- 
Todd

Re: [PATCH v2] github-ci: update macos jobs to macos-15

[Junio C Hamano]

Todd Zullinger <tmz@pobox.com> writes:

> Is it worth using `macos-latest` instead of `macos-26` and
> letting those jobs move along with the current macOS runner
> as it changes?

I am somewhat torn.  Being explicit on both ends would make it
consistent between .gitlab-ci.yml and .github/workflows/main.yml so
that we can more easily compare similar execution between the CI
services offered at two sites.  If we could set to a symbolic name
like "latest" and "oldest-still-supported" on both sites, I would
probably choose that in an instant, though.

[PATCH v3] github-ci: update macos jobs to macos-15

[Junio C Hamano]

GitHub from <no-reply@github.com> address keeps sending

  Subject: [Action Required] macOS 14 hosted runner image is closing down

and suggests to update to either macos-latest (macos-26) or
macos-15.  Use macos-15 for two of the four osx-* jobs, and
macos-latest for the other two jobs, which is very similar to what
.gitlab-ci does.

Because we do not care which exact version we are running, so
request macos-latest instead of naming macos-26.  If there were a
similar symbolic name for the oldest-but-still-supported version,
we would use it instead of explicitly asking for macos-15, but
because there does not appear to be any, request macos-15.  This
would require us to update these two lines once every year, which
is annoying but is manageable.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
 .github/workflows/main.yml | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml
index cf341d74db..7e5769f543 100644
--- a/.github/workflows/main.yml
+++ b/.github/workflows/main.yml
@@ -323,16 +323,16 @@ jobs:
         vector:
           - jobname: osx-clang
             cc: clang
-            pool: macos-14
+            pool: macos-15
           - jobname: osx-reftable
             cc: clang
-            pool: macos-14
+            pool: macos-latest
           - jobname: osx-gcc
             cc: gcc-13
-            pool: macos-14
+            pool: macos-latest
           - jobname: osx-meson
             cc: clang
-            pool: macos-14
+            pool: macos-15
     env:
       CC: ${{matrix.vector.cc}}
       CC_PACKAGE: ${{matrix.vector.cc_package}}

Range-diff against v2:
1:  e28c655dc1 ! 1:  1ac29e72d1 github-ci: update macos jobs to macos-15
    @@ Commit message
     
         and suggests to update to either macos-latest (macos-26) or
         macos-15.  Use macos-15 for two of the four osx-* jobs, and
    -    macos-26 for the other two jobs.
    +    macos-latest for the other two jobs, which is very similar to what
    +    .gitlab-ci does.
    +
    +    Because we do not care which exact version we are running, so
    +    request macos-latest instead of naming macos-26.  If there were a
    +    similar symbolic name for the oldest-but-still-supported version,
    +    we would use it instead of explicitly asking for macos-15, but
    +    because there does not appear to be any, request macos-15.  This
    +    would require us to update these two lines once every year, which
    +    is annoying but is manageable.
     
         Signed-off-by: Junio C Hamano <gitster@pobox.com>
     
    @@ .github/workflows/main.yml: jobs:
                - jobname: osx-reftable
                  cc: clang
     -            pool: macos-14
    -+            pool: macos-26
    ++            pool: macos-latest
                - jobname: osx-gcc
                  cc: gcc-13
     -            pool: macos-14
    -+            pool: macos-26
    ++            pool: macos-latest
                - jobname: osx-meson
                  cc: clang
     -            pool: macos-14
-- 
2.56.0-321-ga7e4057184

Re: [PATCH v2] github-ci: update macos jobs to macos-15

[Patrick Steinhardt]

On Mon, Oct 19, 2026 at 06:14:39PM -0700, Junio C Hamano wrote:
> Todd Zullinger <tmz@pobox.com> writes:
> 
> > Is it worth using `macos-latest` instead of `macos-26` and
> > letting those jobs move along with the current macOS runner
> > as it changes?
> 
> I am somewhat torn.  Being explicit on both ends would make it
> consistent between .gitlab-ci.yml and .github/workflows/main.yml so
> that we can more easily compare similar execution between the CI
> services offered at two sites.  If we could set to a symbolic name
> like "latest" and "oldest-still-supported" on both sites, I would
> probably choose that in an instant, though.

Yeah, unfortunately we don't have "latest" tags on the GitLab side. And
even if we had that it still wouldn't quite help us to keep both sides
comparable as it's very unlikely that GitLab and GitHub have the exact
same schedule for updating the tag.

Comparability to me is an important property as I want to know that a
passing pipeline on the GitLab side will very likely result in a passing
pipeline on the GitHub side. The GitLab pipeline is what my team uses in
day-to-day business, but most of the others in this project typically
use the GitHub pipeline.

So personally I'd keep it at the explicit versions for now so that both
are in sync. We have to bump versions for one of them anyway, so we
should make sure to just bump them both at the same time going forward.

Patrick