Re: [PATCH v2] github-ci: update macos jobs to macos-15
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Oct 20, 2026, 01:14 UTC
- Message-ID
- <xmqqpkx5yxz4.fsf@gitster.g>
- In-Reply-To
- <20261019234724.H0mV3jqQ@teonanacatl.net>
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.