Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: Patrick Steinhardt <ps@pks.im>
Subject: [PATCH v2] github-ci: update macos jobs to macos-15
Date: Mon, 19 Oct 2026 12:41:52 -0700	[thread overview]
Message-ID: <20261019194152.907881-1-gitster@pobox.com> (raw)
In-Reply-To: <xmqqfqy5clgz.fsf@gitster.g>

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


  parent reply	other threads:[~2026-10-19 19:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-16 22:46 [PATCH] github-ci: update macos jobs to macos-15 Junio C Hamano
2026-10-17 13:36 ` brian m. carlson
2026-10-19  7:12 ` Patrick Steinhardt
2026-10-19 18:00   ` Junio C Hamano
2026-10-19 19:41 ` Junio C Hamano [this message]
2026-10-19 23:47   ` [PATCH v2] " Todd Zullinger
2026-10-20  0:30     ` brian m. carlson
2026-10-20  0:54       ` Todd Zullinger
2026-10-20  1:14     ` Junio C Hamano
2026-10-20  5:50       ` Patrick Steinhardt
2026-10-20  4:25 ` [PATCH v3] " Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20261019194152.907881-1-gitster@pobox.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=ps@pks.im \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox