From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] GitHub CI: macos-13 images are no more
Date: Wed, 05 Nov 2025 06:34:30 -0800 [thread overview]
Message-ID: <xmqqo6pgmtu1.fsf@gitster.g> (raw)
In-Reply-To: <xmqqh5v9o0hb.fsf@gitster.g> (Junio C. Hamano's message of "Tue, 04 Nov 2025 15:13:20 -0800")
Junio C Hamano <gitster@pobox.com> writes:
> As this image was deprecated on Sep 22nd, and will be dropped on Dec
> 4th, replace these jobs to use macos-14 images instead.
>
> Signed-off-by: Junio C Hamano <gitster@pobox.com>
> ---
>
> * This is a monkey-see-monkey-do patch. There may be additional
> adjustment necessary (versions of tools available on the system
> may be different, for example).
This, when test-merged to 'master' and also to 'next', seems to be
enough to get GitHub Actions based CI pass. I'll fast-track it in
order to allow us to run it with the upcoming -rc1, and eventually
down to 'maint',
> .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 aa6bce673b..f2af90ad31 100644
> --- a/.github/workflows/main.yml
> +++ b/.github/workflows/main.yml
> @@ -313,16 +313,16 @@ jobs:
> vector:
> - jobname: osx-clang
> cc: clang
> - pool: macos-13
> + pool: macos-14
> - jobname: osx-reftable
> cc: clang
> - pool: macos-13
> + pool: macos-14
> - jobname: osx-gcc
> cc: gcc-13
> - pool: macos-13
> + pool: macos-14
> - jobname: osx-meson
> cc: clang
> - pool: macos-13
> + pool: macos-14
> env:
> CC: ${{matrix.vector.cc}}
> CC_PACKAGE: ${{matrix.vector.cc_package}}
next prev parent reply other threads:[~2025-11-05 14:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 23:13 [PATCH] GitHub CI: macos-13 images are no more Junio C Hamano
2025-11-05 14:34 ` Junio C Hamano [this message]
2025-11-06 7:14 ` Patrick Steinhardt
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=xmqqo6pgmtu1.fsf@gitster.g \
--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;
as well as URLs for NNTP newsgroup(s).