Set cache-bin: false on Swatinem/rust-cache to fix broken cargo on macos-latest#2978
Merged
albertlockett merged 1 commit intoMay 14, 2026
Conversation
…cos-latest runner image
github-actions
Bot
added
the
ci-repo
lalitb
approved these changes
May 14, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2978 +/- ##
==========================================
- Coverage 85.91% 85.90% -0.01%
==========================================
Files 725 725
Lines 275426 275426
==========================================
- Hits 236624 236614 -10
- Misses 38278 38288 +10
Partials 524 524
🚀 New features to boost your workflow:
|
albertlockett
approved these changes
May 14, 2026
albertlockett
approved these changes
May 14, 2026
guancioul
pushed a commit
to guancioul/otel-arrow
that referenced
this pull request
May 16, 2026
…cos-latest (open-telemetry#2978) ## Problem CI `clippy (*, macos-latest)` (and other macOS rust steps) started failing today across many PRs with: ``` error: error: unexpected argument 'clippy' found Usage: rustup-init[EXE] [OPTIONS] ``` ## Root cause GitHub rolled out a new macos-latest runner image today ([actions/runner-images#14037](actions/runner-images#14037)) that changed how the `rustc`/`cargo` rustup proxy binaries are set up. Combined with [Swatinem/rust-cache#325](Swatinem/rust-cache#325) (which made `cache-bin: true` the default in v2.8+), the cached `$CARGO_HOME/bin/` from previous runs gets restored over the freshly-installed proxies, leaving `cargo` dispatching to `rustup-init` behavior instead of the real cargo. Tracked upstream: [Swatinem/rust-cache#341](Swatinem/rust-cache#341). ## Fix Set `cache-bin: false` on all 7 `Swatinem/rust-cache` invocations in `.github/workflows/rust-ci.yml`. This is the workaround confirmed by the upstream issue reporter. We don't `cargo install` any binaries that need caching, so this loses no useful caching.
guancioul
pushed a commit
to guancioul/otel-arrow
that referenced
this pull request
May 16, 2026
…cos-latest (open-telemetry#2978) ## Problem CI `clippy (*, macos-latest)` (and other macOS rust steps) started failing today across many PRs with: ``` error: error: unexpected argument 'clippy' found Usage: rustup-init[EXE] [OPTIONS] ``` ## Root cause GitHub rolled out a new macos-latest runner image today ([actions/runner-images#14037](actions/runner-images#14037)) that changed how the `rustc`/`cargo` rustup proxy binaries are set up. Combined with [Swatinem/rust-cache#325](Swatinem/rust-cache#325) (which made `cache-bin: true` the default in v2.8+), the cached `$CARGO_HOME/bin/` from previous runs gets restored over the freshly-installed proxies, leaving `cargo` dispatching to `rustup-init` behavior instead of the real cargo. Tracked upstream: [Swatinem/rust-cache#341](Swatinem/rust-cache#341). ## Fix Set `cache-bin: false` on all 7 `Swatinem/rust-cache` invocations in `.github/workflows/rust-ci.yml`. This is the workaround confirmed by the upstream issue reporter. We don't `cargo install` any binaries that need caching, so this loses no useful caching.
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
3 participants
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.
Problem
CI
clippy (*, macos-latest)(and other macOS rust steps) started failing today across many PRs with:Root cause
GitHub rolled out a new macos-latest runner image today (actions/runner-images#14037) that changed how the
rustc/cargorustup proxy binaries are set up. Combined with Swatinem/rust-cache#325 (which madecache-bin: truethe default in v2.8+), the cached$CARGO_HOME/bin/from previous runs gets restored over the freshly-installed proxies, leavingcargodispatching torustup-initbehavior instead of the real cargo.Tracked upstream: Swatinem/rust-cache#341.
Fix
Set
cache-bin: falseon all 7Swatinem/rust-cacheinvocations in.github/workflows/rust-ci.yml. This is the workaround confirmed by the upstream issue reporter. We don'tcargo installany binaries that need caching, so this loses no useful caching.