ci(release): make rust-cache restore-only#17
Merged
Conversation
The cache-save post-step (tar of a large release target/) is flaky on Windows runners and red-X'd the release job after the release had already published. Release builds run on tags, so populating the cache buys nothing; restore-only keeps future release runs green.
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.
The
v0.1.5release published successfully, but thebuildjob showed a red X: theSwatinem/rust-cache@v2cache-save post-step (tar of a large releasetarget/) failed on the Windows runner after the release was already created and assets uploaded.Fix: set
save-if: falseon both rust-cache steps inrelease.yml. The release workflow runs only on tags, so populating the cache buys nothing; restore-only avoids the flaky save step and keeps future release runs green.No effect on the release artifacts or the build/test gates - only the post-job cache housekeeping is skipped.