Repository navigation
fix(release): migrate macOS runner and prepare 1.5.0 - #42
Merged
Merged
Conversation
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 v1.4.0 release fails before macOS build starts because GitHub retired macos-14 on November 2, 2026. Switch to the supported macos-15 ARM64 runner and add an unsigned macOS test/build job to PR CI so this path is validated before release.
Bump Cargo, lockfile, both bootstrap defaults, fixture and documentation to 1.5.0.
Validation: both workflow YAML files parse; locked Cargo metadata reports 1.5.0; Linux bootstrap fixture passes; git diff --check passes. Hosted macOS and other CI checks will validate this PR. Signing/notarization remain release-only.
Official notice: https://github.blog/changelog/2026-10-01-github-actions-macos-14-runner-image-retirement/
After merge, release v1.5.0 from the corrected commit. Rerunning the old v1.4.0 tag keeps its old workflow. No tags, releases, merges or deployments performed by this PR preparation.