From: Todd Zullinger <tmz@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Patrick Steinhardt <ps@pks.im>
Subject: Re: [PATCH v2] github-ci: update macos jobs to macos-15
Date: Mon, 19 Oct 2026 20:54:05 -0400 [thread overview]
Message-ID: <20261020005405.yfKQxutD@teonanacatl.net> (raw)
In-Reply-To: <ata2Jg5_0Q6HnN8u@fruit.crustytoothpaste.net>
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
next prev parent reply other threads:[~2026-10-20 0:54 UTC|newest]
Thread overview: 14+ 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 [this message]
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 ` [PATCH v4] github-ci: update macos jobs from macos-14 Junio C Hamano
2026-10-20 17:15 ` 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=20261020005405.yfKQxutD@teonanacatl.net \
--to=tmz@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ps@pks.im \
--cc=sandals@crustytoothpaste.net \
/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