Repository navigation
Split CI and Release workflows, fix macOS builds, allow backfilling releases - #23
Merged
Merged
Conversation
The macos-14 release build job was cancelled before getting a runner in the 0.90 and 0.93 release runs, so neither release was published. MACOSX_DEPLOYMENT_TARGET stays at 14.0 so binaries still run on macOS 14. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UeniBD949fSMpXDs9ZeEx2
macos-26 is the newest arm64 macOS runner; macos-15 is next in line for retirement. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UeniBD949fSMpXDs9ZeEx2
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.
Summary
The
0.90.0-55.2.0and0.93.0-55.2.0tags were created, but neither release was published. In both runs theRelease build (aarch64-apple-darwin)job was cancelled about a second after it was queued. It never got amacos-14runner and left no logs, soPublish binary releasewas skipped:The cause is that GitHub retired all macOS 14 images from Actions on November 2, 2026 (actions/runner-images#13518). Both runs came after that date.
Changes
ci.yml(CI) runs on pull requests and pushes.release.yml(Release) only runs manually frommain. It callsci.ymlthroughworkflow_call, so a release still publishes only after the same checks pass.ci-and-release-tag.ymlis removed.macos-26. It's the newest arm64 macOS runner, andmacos-15will be retired first. The runner is pinned to an exact version, notmacos-latest, so the build image only changes when we change it.MACOSX_DEPLOYMENT_TARGETstays at14.0, so the binaries still run on macOS 14 and newer.taginput on Release. Set it to rebuild and publish an existing tag from that tag's commit. Previously only the version inmain'sCargo.lockcould be released, so 0.90 couldn't be backfilled.main'sCargo.lock, so publishing 0.90 doesn't take "latest" away from 0.93.taginput.After merging
mainwithtagleft empty. This publishes0.93.0-55.2.0and marks it latest.mainagain withtag=0.90.0-55.2.0. This publishes 0.90 without marking it latest.If branch protection requires the old
CIstatus check, confirm it still matches. The job is still namedCI, but checks from the new workflow may show up under a different name.🤖 Generated with Claude Code
https://claude.ai/code/session_01UeniBD949fSMpXDs9ZeEx2