Re: [PATCH v2] github-ci: update macos jobs to macos-15
- From
Todd Zullinger <tmz@pobox.com>
- Date
- Oct 20, 2026, 00:54 UTC
- Message-ID
- <20261020005405.yfKQxutD@teonanacatl.net>
- 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?
[...]
Show 11 quoted lines
>> 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