From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH v4] github-ci: update macos jobs from macos-14
Date: Tue, 20 Oct 2026 08:58:13 -0700 [thread overview]
Message-ID: <20261020155813.3315813-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. Use explicit version number
"26" instead of "latest" so that we can more easily tell the
differences and similarities between github-ci and gitlab-ci
and compare their outcome on the same commit when needed.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
* Hopefully this is the final iteration, and hopefully the later
part of the proposed log message explains the reasoning behind
the choice between latest and 26 well.
.github/workflows/main.yml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml
index 7e5769f543..e8f744d069 100644
--- a/.github/workflows/main.yml
+++ b/.github/workflows/main.yml
@@ -326,10 +326,10 @@ jobs:
pool: macos-15
- jobname: osx-reftable
cc: clang
- pool: macos-latest
+ pool: macos-26
- jobname: osx-gcc
cc: gcc-13
- pool: macos-latest
+ pool: macos-26
- jobname: osx-meson
cc: clang
pool: macos-15
Range-diff against v3:
1: 428ed741e9 ! 1: 2378f810f0 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-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.
+ macos-26 for the other two jobs. Use explicit version number
+ "26" instead of "latest" so that we can more easily tell the
+ differences and similarities between github-ci and gitlab-ci
+ and compare their outcome on the same commit when needed.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
## .github/workflows/main.yml ##
@@ .github/workflows/main.yml: jobs:
- vector:
- - jobname: osx-clang
- cc: clang
-- pool: macos-14
-+ pool: macos-15
+ pool: macos-15
- jobname: osx-reftable
cc: clang
-- pool: macos-14
-+ pool: macos-latest
+- pool: macos-latest
++ pool: macos-26
- jobname: osx-gcc
cc: gcc-13
-- pool: macos-14
-+ pool: macos-latest
+- pool: macos-latest
++ 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}}
+ pool: macos-15
--
2.56.0-321-ga7e4057184
prev parent reply other threads:[~2026-10-20 15:58 UTC|newest]
Thread overview: 13+ 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 ` [PATCH v2] " Junio C Hamano
2026-10-19 23:47 ` 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 14:16 ` Junio C Hamano
2026-10-20 4:25 ` [PATCH v3] " Junio C Hamano
2026-10-20 15:58 ` Junio C Hamano [this message]
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=20261020155813.3315813-1-gitster@pobox.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
/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