Skip to content

Split CI and Release workflows, fix macOS builds, allow backfilling releases - #23

Merged
joseph-isaacs merged 2 commits into
mainfrom
ji/admiring-fermi-l42n6b
Nov 13, 2026
Merged

joseph-isaacs merged 2 commits into
mainfrom
ji/admiring-fermi-l42n6b

Conversation

@joseph-isaacs

@joseph-isaacs joseph-isaacs commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

Summary

The 0.90.0-55.2.0 and 0.93.0-55.2.0 tags were created, but neither release was published. In both runs the Release build (aarch64-apple-darwin) job was cancelled about a second after it was queued. It never got a macos-14 runner and left no logs, so Publish binary release was 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 and release are now separate workflows.
    • ci.yml (CI) runs on pull requests and pushes.
    • release.yml (Release) only runs manually from main. It calls ci.yml through workflow_call, so a release still publishes only after the same checks pass.
    • ci-and-release-tag.yml is removed.
  • macOS runner moves to macos-26. It's the newest arm64 macOS runner, and macos-15 will be retired first. The runner is pinned to an exact version, not macos-latest, so the build image only changes when we change it. MACOSX_DEPLOYMENT_TARGET stays at 14.0, so the binaries still run on macOS 14 and newer.
  • New optional tag input on Release. Set it to rebuild and publish an existing tag from that tag's commit. Previously only the version in main's Cargo.lock could be released, so 0.90 couldn't be backfilled.
    • The tag must already exist; with the input set, the workflow never creates a tag.
    • A backfilled release is marked "latest" only if it matches main's Cargo.lock, so publishing 0.90 doesn't take "latest" away from 0.93.
    • With the input left empty, the workflow behaves as before.
  • The README versioning section is updated for both workflows and the tag input.

After merging

  1. Run Release from main with tag left empty. This publishes 0.93.0-55.2.0 and marks it latest.
  2. Run Release from main again with tag = 0.90.0-55.2.0. This publishes 0.90 without marking it latest.

If branch protection requires the old CI status check, confirm it still matches. The job is still named CI, but checks from the new workflow may show up under a different name.

🤖 Generated with Claude Code

https://claude.ai/code/session_01UeniBD949fSMpXDs9ZeEx2

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
@joseph-isaacs joseph-isaacs changed the title Build macOS release on macos-15 runner Build macOS release on macos-26 runner Nov 13, 2026
@joseph-isaacs
joseph-isaacs merged commit db9433a into main Nov 13, 2026
2 of 3 checks passed
@joseph-isaacs joseph-isaacs changed the title Build macOS release on macos-26 runner Fix macOS release builds and allow backfilling missing releases Nov 13, 2026
@joseph-isaacs joseph-isaacs changed the title Fix macOS release builds and allow backfilling missing releases Split CI and Release workflows, fix macOS builds, allow backfilling releases Nov 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants