ci: drop unused cache from release workflow - #6742
Merged
Merged
Conversation
Release builds run only on v* tag pushes, infrequently enough that any cache entry from the previous release has almost certainly been evicted from the shared 10 GiB GHA cache (LRU eviction, 7-day unused-entry eviction) by the time the next release runs. Every release build is therefore already a cold cache miss, while the cache write still costs multi-GB against the shared quota that ci.yml relies on for its frequent, genuinely cache-effective runs. Removes Swatinem/rust-cache and mozilla-actions/sccache-action from the build-binaries job, and the step-level RUSTC_WRAPPER/SCCACHE_GHA_ENABLED override so the native build step inherits the top-level RUSTC_WRAPPER="" already set for the workflow.
github-actions
Bot
added
documentation
GitHub's windows-11-arm hosted runner reached general availability for public repositories in August 2025, providing a native MSVC ARM64 toolchain and Windows SDK. Build aarch64-pc-windows-msvc natively there instead of leaving the target commented out, since the previous blocker (cross-compiling crypto crates from Linux without Windows ARM64 SDK headers) no longer applies to a native build.
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
1 participant
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
Swatinem/rust-cacheandmozilla-actions/sccache-actionfrom thebuild-binariesjob inrelease.ymlRUSTC_WRAPPER: sccache/SCCACHE_GHA_ENABLED: "true"override on the "Build binary (native)" step, so it correctly inherits the workflow-levelRUSTC_WRAPPER: ""Release builds run only on
v*tag pushes, infrequently enough that any cache entry written by the previous release has almost certainly been evicted from the shared 10 GiB GHA cache (LRU eviction, plus 7-day unused-entry eviction) before the next release runs. Every release build was therefore already a cold cache miss in practice, while still writing a fresh multi-GB cache entry each run that consumes shared cache quotaci.ymldepends on for its frequent, genuinely cache-effective runs.ci.yml,ci-non-linux.yml, and other workflows that run frequently keep their existing caching unchanged — this PR is scoped torelease.yml'sbuild-binariesjob only. Thecrossbuild path never referenced sccache/rust-cache, and no other job inrelease.yml(publish-crates,create-release,docker-publish) usesactions/cache,Swatinem/rust-cache, orsccache.Test plan
fy parse .github/workflows/release.yml— YAML validcrossbuild path unaffected, native build step now correctly inherits top-levelRUSTC_WRAPPER: ""