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

["brian m. carlson" <sandals@crustytoothpaste.net>]

[-- Attachment #1: Type: text/plain, Size: 1497 bytes --]

On 2026-10-19 at 23:47:24, Todd Zullinger wrote:
> I know very, very little about macOS (in general and with
> respect to Github CI)...
> 
> Is it worth using `macos-latest` instead of `macos-26` and
> letting those jobs move along with the current macOS runner
> as it changes?
> 
> The documentation¹ links `macos-latest` to `macos-26` at the
> moment, AFAICT.
> 
> 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.  As far as
POSIX features, it's likely that macOS will stick pretty closely to the
standard because until very recently, it was UNIX certified, so that may
not be a practical concern.

I don't have a very strong opinion about what we should do one way or
the other.  I would be much more likely to want to test across different
versions of Linux, its C libraries, and compilers because there's much
more divergence there in terms of potentially breaking changes and a
much longer lifespan of OS versions.
-- 
brian m. carlson (they/them)
Toronto, Ontario, CA

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 325 bytes --]