{"thread":{"id":"66560","subject":"[PATCH] github-ci: update macos jobs to macos-15","startedAt":"2026-10-16T22:46:36Z","lastAt":"2026-10-21T18:17:12Z","messageCount":17,"participants":["Junio C Hamano","brian m. carlson","Patrick Steinhardt","Todd Zullinger"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"555289","messageId":"xmqqfqy5clgz.fsf@gitster.g","threadId":"66560","inReplyTo":null,"subject":"[PATCH] github-ci: update macos jobs to macos-15","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-10-16T22:46:36Z","receivedAt":"2026-10-16T22:46:36Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"GitHub from <no-reply@github.com> address keeps sending\n\n  Subject: [Action Required] macOS 14 hosted runner image is closing down\n\nand suggests to update to either macos-latest (macos-26) or\nmacos-15.  As we do not have strong reason to pick one over the\nother, this patch picks more conservative choice with hopefully\nsmaller impact.\n\nSigned-off-by: Junio C Hamano <gitster@pobox.com>\n---\n * Not tested at all and I do not do macos myself.\n\n .github/workflows/main.yml | 8 ++++----\n 1 file changed, 4 insertions(+), 4 deletions(-)\n\ndiff --git i/.github/workflows/main.yml w/.github/workflows/main.yml\nindex b229739be8..d69f6f2b10 100644\n--- i/.github/workflows/main.yml\n+++ w/.github/workflows/main.yml\n@@ -349,16 +349,16 @@ jobs:\n         vector:\n           - jobname: osx-clang\n             cc: clang\n-            pool: macos-14\n+            pool: macos-15\n           - jobname: osx-reftable\n             cc: clang\n-            pool: macos-14\n+            pool: macos-15\n           - jobname: osx-gcc\n             cc: gcc-13\n-            pool: macos-14\n+            pool: macos-15\n           - jobname: osx-meson\n             cc: clang\n-            pool: macos-14\n+            pool: macos-15\n     env:\n       CC: ${{matrix.vector.cc}}\n       CC_PACKAGE: ${{matrix.vector.cc_package}}\n\n"},{"id":"555327","messageId":"atN52HNEzdSeh19l@fruit.crustytoothpaste.net","threadId":"66560","inReplyTo":"xmqqfqy5clgz.fsf@gitster.g","subject":"Re: [PATCH] github-ci: update macos jobs to macos-15","fromName":"brian m. carlson","fromEmail":"sandals@crustytoothpaste.net","sentAt":"2026-10-17T13:36:25Z","receivedAt":"2026-10-17T13:36:25Z","isPatch":true,"sender":{"key":"sandals@crustytoothpaste.net","avatar":"https://avatars.githubusercontent.com/u/497054?v=4"},"body":"On 2026-10-16 at 22:46:36, Junio C Hamano wrote:\n> GitHub from <no-reply@github.com> address keeps sending\n> \n>   Subject: [Action Required] macOS 14 hosted runner image is closing down\n> \n> and suggests to update to either macos-latest (macos-26) or\n> macos-15.  As we do not have strong reason to pick one over the\n> other, this patch picks more conservative choice with hopefully\n> smaller impact.\n> \n> Signed-off-by: Junio C Hamano <gitster@pobox.com>\n> ---\n>  * Not tested at all and I do not do macos myself.\n\nI think this is fine if it passes CI.  There's not that much of a\ndifference in terms of POSIX-related functionality in different versions\nof macOS, so upgrading to macOS 15 shouldn't be a problem.  I think 15\nis a better option than 26 because we're more likely to avoid anything\nnew that older versions don't have.\n-- \nbrian m. carlson (they/them)\nToronto, Ontario, CA\n"},{"id":"555392","messageId":"atXC91tL7MHRioPZ@pks.im","threadId":"66560","inReplyTo":"xmqqfqy5clgz.fsf@gitster.g","subject":"Re: [PATCH] github-ci: update macos jobs to macos-15","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-19T07:12:55Z","receivedAt":"2026-10-19T07:12:55Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Fri, Oct 16, 2026 at 03:46:36PM -0700, Junio C Hamano wrote:\n> diff --git i/.github/workflows/main.yml w/.github/workflows/main.yml\n> index b229739be8..d69f6f2b10 100644\n> --- i/.github/workflows/main.yml\n> +++ w/.github/workflows/main.yml\n> @@ -349,16 +349,16 @@ jobs:\n>          vector:\n>            - jobname: osx-clang\n>              cc: clang\n> -            pool: macos-14\n> +            pool: macos-15\n>            - jobname: osx-reftable\n>              cc: clang\n> -            pool: macos-14\n> +            pool: macos-15\n>            - jobname: osx-gcc\n>              cc: gcc-13\n> -            pool: macos-14\n> +            pool: macos-15\n>            - jobname: osx-meson\n>              cc: clang\n> -            pool: macos-14\n> +            pool: macos-15\n\nDo we maybe want to update those jobs to use a mixture of macos-15 and\nmacos-26? In GitLab CI we use macos-15 for osx-clang and macos-26 for\neverything else. Like that we have higher test coverage compared to only\nexercising one major release.\n\nPatrick\n\n"},{"id":"555444","messageId":"xmqqy0bt4llp.fsf@gitster.g","threadId":"66560","inReplyTo":"atXC91tL7MHRioPZ@pks.im","subject":"Re: [PATCH] github-ci: update macos jobs to macos-15","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-10-19T18:00:02Z","receivedAt":"2026-10-19T18:00:02Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Patrick Steinhardt <ps@pks.im> writes:\n\n>>            - jobname: osx-meson\n>>              cc: clang\n>> -            pool: macos-14\n>> +            pool: macos-15\n>\n> Do we maybe want to update those jobs to use a mixture of macos-15 and\n> macos-26? In GitLab CI we use macos-15 for osx-clang and macos-26 for\n> everything else. Like that we have higher test coverage compared to only\n> exercising one major release.\n\nI do not care too deeply, but variety is better than monoculture.\nLet me roll a die and send v2 ;-)\n\nThanks.\n\n"},{"id":"555451","messageId":"20261019194152.907881-1-gitster@pobox.com","threadId":"66560","inReplyTo":"xmqqfqy5clgz.fsf@gitster.g","subject":"[PATCH v2] github-ci: update macos jobs to macos-15","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-10-19T19:41:52Z","receivedAt":"2026-10-19T19:41:52Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"GitHub from <no-reply@github.com> address keeps sending\n\n  Subject: [Action Required] macOS 14 hosted runner image is closing down\n\nand suggests to update to either macos-latest (macos-26) or\nmacos-15.  Use macos-15 for two of the four osx-* jobs, and\nmacos-26 for the other two jobs.\n\nSigned-off-by: Junio C Hamano <gitster@pobox.com>\n---\n .github/workflows/main.yml | 8 ++++----\n 1 file changed, 4 insertions(+), 4 deletions(-)\n\ndiff --git a/.github/workflows/main.yml b/.github/workflows/main.yml\nindex cf341d74db..e8f744d069 100644\n--- a/.github/workflows/main.yml\n+++ b/.github/workflows/main.yml\n@@ -323,16 +323,16 @@ jobs:\n         vector:\n           - jobname: osx-clang\n             cc: clang\n-            pool: macos-14\n+            pool: macos-15\n           - jobname: osx-reftable\n             cc: clang\n-            pool: macos-14\n+            pool: macos-26\n           - jobname: osx-gcc\n             cc: gcc-13\n-            pool: macos-14\n+            pool: macos-26\n           - jobname: osx-meson\n             cc: clang\n-            pool: macos-14\n+            pool: macos-15\n     env:\n       CC: ${{matrix.vector.cc}}\n       CC_PACKAGE: ${{matrix.vector.cc_package}}\n\nRange-diff against v1:\n1:  c7124011e9 ! 1:  7ca9f53bab github-ci: update macos jobs to macos-15\n    @@ Commit message\n           Subject: [Action Required] macOS 14 hosted runner image is closing down\n     \n         and suggests to update to either macos-latest (macos-26) or\n    -    macos-15.  As we do not have strong reason to pick one over the\n    -    other, this patch picks more conservative choice with hopefully\n    -    smaller impact.\n    +    macos-15.  Use macos-15 for two of the four osx-* jobs, and\n    +    macos-26 for the other two jobs.\n     \n         Signed-off-by: Junio C Hamano <gitster@pobox.com>\n     \n    @@ .github/workflows/main.yml: jobs:\n                - jobname: osx-reftable\n                  cc: clang\n     -            pool: macos-14\n    -+            pool: macos-15\n    ++            pool: macos-26\n                - jobname: osx-gcc\n                  cc: gcc-13\n     -            pool: macos-14\n    -+            pool: macos-15\n    ++            pool: macos-26\n                - jobname: osx-meson\n                  cc: clang\n     -            pool: macos-14\n-- \n2.56.0-314-g110ce7813b\n\n\n"},{"id":"555482","messageId":"20261019234724.H0mV3jqQ@teonanacatl.net","threadId":"66560","inReplyTo":"20261019194152.907881-1-gitster@pobox.com","subject":"Re: [PATCH v2] github-ci: update macos jobs to macos-15","fromName":"Todd Zullinger","fromEmail":"tmz@pobox.com","sentAt":"2026-10-19T23:47:24Z","receivedAt":"2026-10-19T23:47:24Z","isPatch":true,"sender":{"key":"tmz@pobox.com","avatar":"https://avatars.githubusercontent.com/u/806319?v=4"},"body":"Junio C Hamano wrote:\n> GitHub from <no-reply@github.com> address keeps sending\n> \n>   Subject: [Action Required] macOS 14 hosted runner image is closing down\n> \n> and suggests to update to either macos-latest (macos-26) or\n> macos-15.  Use macos-15 for two of the four osx-* jobs, and\n> macos-26 for the other two jobs.\n\nI know very, very little about macOS (in general and with\nrespect to Github CI)...\n\nIs it worth using `macos-latest` instead of `macos-26` and\nletting those jobs move along with the current macOS runner\nas it changes?\n\nThe documentationï¿½ links `macos-latest` to `macos-26` at the\nmoment, AFAICT.\n\nI don't know if that moves to the next release too quickly\nto be useful to Git or not.  If not, maybe using that will\nbe a more convenient way to get macOS coverage where we\ndon't have a strong preference for the version?\n\nï¿½ https://docs.github.com/en/actions/reference/runners/github-hosted-runners#standard-github-hosted-runners-for-public-repositories\n\n-- \nTodd\n\n"},{"id":"555483","messageId":"ata2Jg5_0Q6HnN8u@fruit.crustytoothpaste.net","threadId":"66560","inReplyTo":"20261019234724.H0mV3jqQ@teonanacatl.net","subject":"Re: [PATCH v2] github-ci: update macos jobs to macos-15","fromName":"brian m. carlson","fromEmail":"sandals@crustytoothpaste.net","sentAt":"2026-10-20T00:30:30Z","receivedAt":"2026-10-20T00:30:30Z","isPatch":true,"sender":{"key":"sandals@crustytoothpaste.net","avatar":"https://avatars.githubusercontent.com/u/497054?v=4"},"body":"On 2026-10-19 at 23:47:24, Todd Zullinger wrote:\n> I know very, very little about macOS (in general and with\n> respect to Github CI)...\n> \n> Is it worth using `macos-latest` instead of `macos-26` and\n> letting those jobs move along with the current macOS runner\n> as it changes?\n> \n> The documentation¹ links `macos-latest` to `macos-26` at the\n> moment, AFAICT.\n> \n> I don't know if that moves to the next release too quickly\n> to be useful to Git or not.  If not, maybe using that will\n> be a more convenient way to get macOS coverage where we\n> don't have a strong preference for the version?\n\nI believe macOS releases once a year, so I expect that the macOS version\nfor GitHub Actions will update about once a year as well and that one\nversion a year will be removed.\n\nUsing `macos-latest` would be the easiest way to keep up to date, but it\nwould also mean that we wouldn't test older OS features.  As far as\nPOSIX features, it's likely that macOS will stick pretty closely to the\nstandard because until very recently, it was UNIX certified, so that may\nnot be a practical concern.\n\nI don't have a very strong opinion about what we should do one way or\nthe other.  I would be much more likely to want to test across different\nversions of Linux, its C libraries, and compilers because there's much\nmore divergence there in terms of potentially breaking changes and a\nmuch longer lifespan of OS versions.\n-- \nbrian m. carlson (they/them)\nToronto, Ontario, CA\n"},{"id":"555484","messageId":"20261020005405.yfKQxutD@teonanacatl.net","threadId":"66560","inReplyTo":"ata2Jg5_0Q6HnN8u@fruit.crustytoothpaste.net","subject":"Re: [PATCH v2] github-ci: update macos jobs to macos-15","fromName":"Todd Zullinger","fromEmail":"tmz@pobox.com","sentAt":"2026-10-20T00:54:05Z","receivedAt":"2026-10-20T00:54:05Z","isPatch":true,"sender":{"key":"tmz@pobox.com","avatar":"https://avatars.githubusercontent.com/u/806319?v=4"},"body":"brian m. carlson wrote:\n> On 2026-10-19 at 23:47:24, Todd Zullinger wrote:\n>> Is it worth using `macos-latest` instead of `macos-26` and\n>> letting those jobs move along with the current macOS runner\n>> as it changes?\n[...]\n>> I don't know if that moves to the next release too quickly\n>> to be useful to Git or not.  If not, maybe using that will\n>> be a more convenient way to get macOS coverage where we\n>> don't have a strong preference for the version?\n> \n> I believe macOS releases once a year, so I expect that the macOS version\n> for GitHub Actions will update about once a year as well and that one\n> version a year will be removed.\n> \n> Using `macos-latest` would be the easiest way to keep up to date, but it\n> would also mean that we wouldn't test older OS features.\n\nThat's where the macos-15 jobs take effect.  To be sure, I\nwasn't suggesting setting all of them to latest, just those\nwhich are set to macos-26 here, as a way to get rolling\ntesting on macOS.\n\n-- \nTodd\n\n"},{"id":"555485","messageId":"xmqqpkx5yxz4.fsf@gitster.g","threadId":"66560","inReplyTo":"20261019234724.H0mV3jqQ@teonanacatl.net","subject":"Re: [PATCH v2] github-ci: update macos jobs to macos-15","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-10-20T01:14:39Z","receivedAt":"2026-10-20T01:14:39Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Todd Zullinger <tmz@pobox.com> writes:\n\n> Is it worth using `macos-latest` instead of `macos-26` and\n> letting those jobs move along with the current macOS runner\n> as it changes?\n\nI am somewhat torn.  Being explicit on both ends would make it\nconsistent between .gitlab-ci.yml and .github/workflows/main.yml so\nthat we can more easily compare similar execution between the CI\nservices offered at two sites.  If we could set to a symbolic name\nlike \"latest\" and \"oldest-still-supported\" on both sites, I would\nprobably choose that in an instant, though.\n\n"},{"id":"555493","messageId":"20261020042546.2854586-1-gitster@pobox.com","threadId":"66560","inReplyTo":"xmqqfqy5clgz.fsf@gitster.g","subject":"[PATCH v3] github-ci: update macos jobs to macos-15","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-10-20T04:25:46Z","receivedAt":"2026-10-20T04:25:46Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"GitHub from <no-reply@github.com> address keeps sending\n\n  Subject: [Action Required] macOS 14 hosted runner image is closing down\n\nand suggests to update to either macos-latest (macos-26) or\nmacos-15.  Use macos-15 for two of the four osx-* jobs, and\nmacos-latest for the other two jobs, which is very similar to what\n.gitlab-ci does.\n\nBecause we do not care which exact version we are running, so\nrequest macos-latest instead of naming macos-26.  If there were a\nsimilar symbolic name for the oldest-but-still-supported version,\nwe would use it instead of explicitly asking for macos-15, but\nbecause there does not appear to be any, request macos-15.  This\nwould require us to update these two lines once every year, which\nis annoying but is manageable.\n\nSigned-off-by: Junio C Hamano <gitster@pobox.com>\n---\n .github/workflows/main.yml | 8 ++++----\n 1 file changed, 4 insertions(+), 4 deletions(-)\n\ndiff --git a/.github/workflows/main.yml b/.github/workflows/main.yml\nindex cf341d74db..7e5769f543 100644\n--- a/.github/workflows/main.yml\n+++ b/.github/workflows/main.yml\n@@ -323,16 +323,16 @@ jobs:\n         vector:\n           - jobname: osx-clang\n             cc: clang\n-            pool: macos-14\n+            pool: macos-15\n           - jobname: osx-reftable\n             cc: clang\n-            pool: macos-14\n+            pool: macos-latest\n           - jobname: osx-gcc\n             cc: gcc-13\n-            pool: macos-14\n+            pool: macos-latest\n           - jobname: osx-meson\n             cc: clang\n-            pool: macos-14\n+            pool: macos-15\n     env:\n       CC: ${{matrix.vector.cc}}\n       CC_PACKAGE: ${{matrix.vector.cc_package}}\n\nRange-diff against v2:\n1:  e28c655dc1 ! 1:  1ac29e72d1 github-ci: update macos jobs to macos-15\n    @@ Commit message\n     \n         and suggests to update to either macos-latest (macos-26) or\n         macos-15.  Use macos-15 for two of the four osx-* jobs, and\n    -    macos-26 for the other two jobs.\n    +    macos-latest for the other two jobs, which is very similar to what\n    +    .gitlab-ci does.\n    +\n    +    Because we do not care which exact version we are running, so\n    +    request macos-latest instead of naming macos-26.  If there were a\n    +    similar symbolic name for the oldest-but-still-supported version,\n    +    we would use it instead of explicitly asking for macos-15, but\n    +    because there does not appear to be any, request macos-15.  This\n    +    would require us to update these two lines once every year, which\n    +    is annoying but is manageable.\n     \n         Signed-off-by: Junio C Hamano <gitster@pobox.com>\n     \n    @@ .github/workflows/main.yml: jobs:\n                - jobname: osx-reftable\n                  cc: clang\n     -            pool: macos-14\n    -+            pool: macos-26\n    ++            pool: macos-latest\n                - jobname: osx-gcc\n                  cc: gcc-13\n     -            pool: macos-14\n    -+            pool: macos-26\n    ++            pool: macos-latest\n                - jobname: osx-meson\n                  cc: clang\n     -            pool: macos-14\n-- \n2.56.0-321-ga7e4057184\n\n\n"},{"id":"555495","messageId":"atcBKeaaEAfCez9q@pks.im","threadId":"66560","inReplyTo":"xmqqpkx5yxz4.fsf@gitster.g","subject":"Re: [PATCH v2] github-ci: update macos jobs to macos-15","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-20T05:50:33Z","receivedAt":"2026-10-20T05:50:33Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Mon, Oct 19, 2026 at 06:14:39PM -0700, Junio C Hamano wrote:\n> Todd Zullinger <tmz@pobox.com> writes:\n> \n> > Is it worth using `macos-latest` instead of `macos-26` and\n> > letting those jobs move along with the current macOS runner\n> > as it changes?\n> \n> I am somewhat torn.  Being explicit on both ends would make it\n> consistent between .gitlab-ci.yml and .github/workflows/main.yml so\n> that we can more easily compare similar execution between the CI\n> services offered at two sites.  If we could set to a symbolic name\n> like \"latest\" and \"oldest-still-supported\" on both sites, I would\n> probably choose that in an instant, though.\n\nYeah, unfortunately we don't have \"latest\" tags on the GitLab side. And\neven if we had that it still wouldn't quite help us to keep both sides\ncomparable as it's very unlikely that GitLab and GitHub have the exact\nsame schedule for updating the tag.\n\nComparability to me is an important property as I want to know that a\npassing pipeline on the GitLab side will very likely result in a passing\npipeline on the GitHub side. The GitLab pipeline is what my team uses in\nday-to-day business, but most of the others in this project typically\nuse the GitHub pipeline.\n\nSo personally I'd keep it at the explicit versions for now so that both\nare in sync. We have to bump versions for one of them anyway, so we\nshould make sure to just bump them both at the same time going forward.\n\nPatrick\n\n"},{"id":"555550","messageId":"xmqq1p9kzcbt.fsf@gitster.g","threadId":"66560","inReplyTo":"atcBKeaaEAfCez9q@pks.im","subject":"Re: [PATCH v2] github-ci: update macos jobs to macos-15","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-10-20T14:16:54Z","receivedAt":"2026-10-20T14:16:54Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Patrick Steinhardt <ps@pks.im> writes:\n\n> So personally I'd keep it at the explicit versions for now so that both\n> are in sync. We have to bump versions for one of them anyway, so we\n> should make sure to just bump them both at the same time going forward.\n\n... or deliberately make them diverge for more variety.  I'll drop\nthe v3 patch and use v2.\n\nThanks.\n\n"},{"id":"555570","messageId":"20261020155813.3315813-1-gitster@pobox.com","threadId":"66560","inReplyTo":"xmqqfqy5clgz.fsf@gitster.g","subject":"[PATCH v4] github-ci: update macos jobs from macos-14","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-10-20T15:58:13Z","receivedAt":"2026-10-20T15:58:13Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"GitHub from <no-reply@github.com> address keeps sending\n\n  Subject: [Action Required] macOS 14 hosted runner image is closing down\n\nand suggests to update to either macos-latest (macos-26) or\nmacos-15.  Use macos-15 for two of the four osx-* jobs, and\nmacos-26 for the other two jobs.  Use explicit version number\n\"26\" instead of \"latest\" so that we can more easily tell the\ndifferences and similarities between github-ci and gitlab-ci\nand compare their outcome on the same commit when needed.\n\nSigned-off-by: Junio C Hamano <gitster@pobox.com>\n---\n\n * Hopefully this is the final iteration, and hopefully the later\n   part of the proposed log message explains the reasoning behind\n   the choice between latest and 26 well.\n\n .github/workflows/main.yml | 4 ++--\n 1 file changed, 2 insertions(+), 2 deletions(-)\n\ndiff --git a/.github/workflows/main.yml b/.github/workflows/main.yml\nindex 7e5769f543..e8f744d069 100644\n--- a/.github/workflows/main.yml\n+++ b/.github/workflows/main.yml\n@@ -326,10 +326,10 @@ jobs:\n             pool: macos-15\n           - jobname: osx-reftable\n             cc: clang\n-            pool: macos-latest\n+            pool: macos-26\n           - jobname: osx-gcc\n             cc: gcc-13\n-            pool: macos-latest\n+            pool: macos-26\n           - jobname: osx-meson\n             cc: clang\n             pool: macos-15\n\nRange-diff against v3:\n1:  428ed741e9 ! 1:  2378f810f0 github-ci: update macos jobs to macos-15\n    @@ Commit message\n     \n         and suggests to update to either macos-latest (macos-26) or\n         macos-15.  Use macos-15 for two of the four osx-* jobs, and\n    -    macos-latest for the other two jobs, which is very similar to what\n    -    .gitlab-ci does.\n    -\n    -    Because we do not care which exact version we are running, so\n    -    request macos-latest instead of naming macos-26.  If there were a\n    -    similar symbolic name for the oldest-but-still-supported version,\n    -    we would use it instead of explicitly asking for macos-15, but\n    -    because there does not appear to be any, request macos-15.  This\n    -    would require us to update these two lines once every year, which\n    -    is annoying but is manageable.\n    +    macos-26 for the other two jobs.  Use explicit version number\n    +    \"26\" instead of \"latest\" so that we can more easily tell the\n    +    differences and similarities between github-ci and gitlab-ci\n    +    and compare their outcome on the same commit when needed.\n     \n         Signed-off-by: Junio C Hamano <gitster@pobox.com>\n     \n      ## .github/workflows/main.yml ##\n     @@ .github/workflows/main.yml: jobs:\n    -         vector:\n    -           - jobname: osx-clang\n    -             cc: clang\n    --            pool: macos-14\n    -+            pool: macos-15\n    +             pool: macos-15\n                - jobname: osx-reftable\n                  cc: clang\n    --            pool: macos-14\n    -+            pool: macos-latest\n    +-            pool: macos-latest\n    ++            pool: macos-26\n                - jobname: osx-gcc\n                  cc: gcc-13\n    --            pool: macos-14\n    -+            pool: macos-latest\n    +-            pool: macos-latest\n    ++            pool: macos-26\n                - jobname: osx-meson\n                  cc: clang\n    --            pool: macos-14\n    -+            pool: macos-15\n    -     env:\n    -       CC: ${{matrix.vector.cc}}\n    -       CC_PACKAGE: ${{matrix.vector.cc_package}}\n    +             pool: macos-15\n-- \n2.56.0-321-ga7e4057184\n\n\n"},{"id":"555585","messageId":"xmqqv76wwax4.fsf@gitster.g","threadId":"66560","inReplyTo":"20261020155813.3315813-1-gitster@pobox.com","subject":"Re: [PATCH v4] github-ci: update macos jobs from macos-14","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-10-20T17:15:35Z","receivedAt":"2026-10-20T17:15:35Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Junio C Hamano <gitster@pobox.com> writes:\n\n> GitHub from <no-reply@github.com> address keeps sending\n>\n>   Subject: [Action Required] macOS 14 hosted runner image is closing down\n>\n> and suggests to update to either macos-latest (macos-26) or\n> macos-15.  Use macos-15 for two of the four osx-* jobs, and\n> macos-26 for the other two jobs.  Use explicit version number\n> \"26\" instead of \"latest\" so that we can more easily tell the\n> differences and similarities between github-ci and gitlab-ci\n> and compare their outcome on the same commit when needed.\n>\n> Signed-off-by: Junio C Hamano <gitster@pobox.com>\n> ---\n>\n>  * Hopefully this is the final iteration, and hopefully the later\n>    part of the proposed log message explains the reasoning behind\n>    the choice between latest and 26 well.\n\nNah, sorry, this patch was bogus.\n\n"},{"id":"555646","messageId":"xmqqa4o7sp0j.fsf@gitster.g","threadId":"66560","inReplyTo":"xmqqfqy5clgz.fsf@gitster.g","subject":"[PATCH v5] github-ci: update macos jobs to macos-15","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-10-21T03:37:00Z","receivedAt":"2026-10-21T03:37:00Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"GitHub from <no-reply@github.com> address keeps sending\n\n  Subject: [Action Required] macOS 14 hosted runner image is closing down\n\nand suggests to update to either macos-latest (macos-26) or\nmacos-15.  Use macos-15 for two of the four osx-* jobs, and\nmacos-26 for the other two jobs.  Use explicit version number\n\"26\" instead of \"latest\" so that we can more easily tell the\ndifferences and similarities between github-ci and gitlab-ci\nand compare their outcome on the same commit when needed.\n\nSigned-off-by: Junio C Hamano <gitster@pobox.com>\n---\n .github/workflows/main.yml | 8 ++++----\n 1 file changed, 4 insertions(+), 4 deletions(-)\n\ndiff --git a/.github/workflows/main.yml b/.github/workflows/main.yml\nindex b229739be8..f37834326f 100644\n--- a/.github/workflows/main.yml\n+++ b/.github/workflows/main.yml\n@@ -349,16 +349,16 @@ jobs:\n         vector:\n           - jobname: osx-clang\n             cc: clang\n-            pool: macos-14\n+            pool: macos-15\n           - jobname: osx-reftable\n             cc: clang\n-            pool: macos-14\n+            pool: macos-26\n           - jobname: osx-gcc\n             cc: gcc-13\n-            pool: macos-14\n+            pool: macos-26\n           - jobname: osx-meson\n             cc: clang\n-            pool: macos-14\n+            pool: macos-15\n     env:\n       CC: ${{matrix.vector.cc}}\n       CC_PACKAGE: ${{matrix.vector.cc_package}}\n-- \n2.56.0-321-ga7e4057184\n\n\n"},{"id":"555691","messageId":"athwcntchANgnJxD@pks.im","threadId":"66560","inReplyTo":"xmqqa4o7sp0j.fsf@gitster.g","subject":"Re: [PATCH v5] github-ci: update macos jobs to macos-15","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-10-21T07:57:38Z","receivedAt":"2026-10-21T07:57:38Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Tue, Oct 20, 2026 at 08:37:00PM -0700, Junio C Hamano wrote:\n> GitHub from <no-reply@github.com> address keeps sending\n> \n>   Subject: [Action Required] macOS 14 hosted runner image is closing down\n> \n> and suggests to update to either macos-latest (macos-26) or\n> macos-15.  Use macos-15 for two of the four osx-* jobs, and\n> macos-26 for the other two jobs.  Use explicit version number\n> \"26\" instead of \"latest\" so that we can more easily tell the\n> differences and similarities between github-ci and gitlab-ci\n> and compare their outcome on the same commit when needed.\n\nThanks, this version looks good to me.\n\nPatrick\n\n"},{"id":"555771","messageId":"xmqqmrs6or4n.fsf@gitster.g","threadId":"66560","inReplyTo":"athwcntchANgnJxD@pks.im","subject":"Re: [PATCH v5] github-ci: update macos jobs to macos-15","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-10-21T18:17:12Z","receivedAt":"2026-10-21T18:17:12Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Patrick Steinhardt <ps@pks.im> writes:\n\n> On Tue, Oct 20, 2026 at 08:37:00PM -0700, Junio C Hamano wrote:\n>> GitHub from <no-reply@github.com> address keeps sending\n>> \n>>   Subject: [Action Required] macOS 14 hosted runner image is closing down\n>> \n>> and suggests to update to either macos-latest (macos-26) or\n>> macos-15.  Use macos-15 for two of the four osx-* jobs, and\n>> macos-26 for the other two jobs.  Use explicit version number\n>> \"26\" instead of \"latest\" so that we can more easily tell the\n>> differences and similarities between github-ci and gitlab-ci\n>> and compare their outcome on the same commit when needed.\n>\n> Thanks, this version looks good to me.\n\nThanks.  I'll retitle \"jobs from macos-14\" instead as we update some\nto 15 and others to 26.\n\n"}]}