Repository navigation
fix(ci): macOS 15 runner and SHA-pinned actions - #3
Merged
Merged
Conversation
macos-14 was retired on 2026-11-02 and its brownout window kills the job in one second, so the arm64 build never ran and the release never published. macos-15 is the arm64 image and stays supported.
MihaiNueleanu
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The arm64 job died in one second because
macos-14is in its retirement brownout (image unsupported from 2026-11-02, actions/runner-images#13518). The linux leg built fine, sopublishwas skipped and no release went out.Runner
macos-14->macos-15, which is the arm64 image (macos-15-intelis x64,macos-26is newest), with a comment so the next person does not reach formacos-latestor an Intel label.Actions, versioned and pinned (tag in a comment, commit SHA in
uses:so a repointed tag cannot swap code under the build)toolchain: stableset explicitlyThese also clear the Node 20 deprecation annotations, since all of them now run on Node 24. One behaviour change to note:
download-artifact@v8fails the run on a digest mismatch instead of warning.Unproven until it runs on
main: GitHub does not executerelease.yamlfrom a branch, so the first real test is the merge, and that run also produces the release the failed one skipped.