Repository navigation
CI saves Rust caches only on dev, releases save none on tags - #292
Merged
Merged
Conversation
- ci.yml: `rust-cache` saves only on pushes to dev. A PR reads its own caches, its base branch's (dev) and the default branch's (main), never another PR's, so a cache saved on a PR served only a later push to that same PR while taking as much of the 10 GB quota as dev's. main is only ever fast-forwarded to a dev commit, so its caches duplicated dev's. - release.yml: no cache is saved on tags. A tag run's cache is filed under that tag and no later tag can read it; v2026.10.7 left 3.3 GB. Rehearsal branches still save, since a rehearsal often takes several pushes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
rust-cachesaves only on pushes to dev. A PR reads its owncaches, its base branch's (dev) and the default branch's (main), never
another PR's, so a cache saved on a PR served only a later push to that same
PR while taking as much of the 10 GB quota as dev's. main is only ever
fast-forwarded to a dev commit, so its caches duplicated dev's.
that tag and no later tag can read it; v2026.10.7 left 3.3 GB. Rehearsal
branches still save, since a rehearsal often takes several pushes.
🤖 Generated with Claude Code