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

[Patrick Steinhardt <ps@pks.im>]

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