No more osx13 labels in release CI

[targos]

See https://ci-release.nodejs.org/job/iojs+release/11311/

This is the release job for v24.10.0. There are no macOS builds because the osx13 labels have disappeared.

/cc @ryanaslett

[MikeMcC399]

@targos

See https://ci-release.nodejs.org/job/iojs+release/11311/

This is the release job for v24.10.0. There are no macOS builds because the osx13 labels have disappeared.

Thanks for the cross-reference in nodejs/node#60176!

GitHub Actions has also deprecated macOS 13 runner images GitHub Actions: macOS 13 runner image is closing down, so it would be good to remove any reliance of this macOS version. Edit: mentioned here just for comparison

https://endoflife.date/macos shows Service Status for macOS 13 (Ventura) ended on Sep 15, 2025. I guess due to the release of macOS 26; with the latest 3 releases now being macOS 26 (Tahoe), 15 (Sequoia) and 14 (Sonoma).

[ssbarnea]

As a hint, renovate is quite good at updating github runners versions too.

[MikeMcC399]

@ssbarnea

As a hint, renovate is quite good at updating github runners versions too.

Not sure that is relevant here though, since this is a Jenkins environment. I only mentioned GitHub Actions as a comparison, not as a source of the issue.

[ryanaslett]

I was under the mistaken impression that the build exclusion script only applied to the test instances, and assumed the macos15 images could/would build the releases <node25.

I have re-enabled the osx13 release images and am re-running the osx13 labeled portions of that job. (osx13-release-pkg, osx13-arm64-release-tar, osx13-x64-release-tar)

[ryanaslett]

The tags are back, and the https://ci-release.nodejs.org/job/iojs+release/11318/ job for the osx13 environments ran successfully, but Im not sure if something needs to still happen to promote them to the website I still see

[UlisesGascon]

Im not sure if something needs to still happen to promote them to the website I still see

Yep! @RafaelGSS will need to rerun from step 15 (https://github.com/nodejs/node/blob/main/doc/contributing/releases.md#15-promote-and-sign-the-release-builds) if I am not mistaken.

[RafaelGSS]

I'm about to promote it again, but the warning seems I'll override the existing builds (like rhel, windows)...

... Expecting a total of 38 assets for v24.x
... 5 assets waiting in staging
... 33 assets already promoted
 ✓  Complete set of expected assets in place for v24.x
... Checking R2 assets
... Expecting a total of 38 assets for v24.x
... 38 assets waiting in R2 staging
 ⚠  33 assets already promoted in R2 will be overwritten, is this OK?
 ✓  Complete set of expected assets in place for v24.x
    Promote if you are certain this is the the correct course of action