Repository navigation
ci: modernize release workflow for current runners and actions - #2
Merged
Merged
Conversation
Replace retired macos-12 runners with native macos-13 (x86_64) and macos-14 (aarch64); bump actions/checkout v3 -> v5, actions/upload-artifact v3 -> v4, and softprops/action-gh-release v1 -> v2. Give each matrix job a unique artifact name (upload-artifact v4 requires it), install the build target via setup-rust-toolchain instead of a separate rustup step, and install libxdo-dev in the publish-crate job so the crates.io verification build can link enigo.
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.
Fixes the bit-rotted
release.ymlso a futurev*tag actually produces binaries and publishes to crates.io. No tag is being cut here — this just gets the pipeline ready.Changes
macos-12→ nativemacos-13(x86_64) +macos-14(aarch64). The macos-12 image no longer exists, so the macOS build jobs couldn't start.actions/checkoutv3 → v5,actions/upload-artifactv3 → v4 (v3 is disabled by GitHub),softprops/action-gh-releasev1 → v2.release-<target>); v4 rejects multiple jobs writing the same artifact name.setup-rust-toolchain'starget:input instead of a separaterustup target addstep (targets are now native to each runner anyway).libxdo-devbeforecargo publishso the crates.io verification build can linkenigoon Linux.Notes
Release flow is unchanged: pushing a
v0.2.0tag builds all four targets, creates a draft GitHub release, and publisheskeep-activeto crates.io. Cutting that tag is intentionally left for a follow-up.