Skip to content

ci: retire low-frequency release target caches - #1226

Merged
zackees merged 1 commit into
mainfrom
fix/1216-release-cache-budget
Sep 27, 2026
Merged

zackees merged 1 commit into
mainfrom
fix/1216-release-cache-budget

Conversation

@zackees

@zackees zackees commented Sep 27, 2026

Copy link
Copy Markdown
Owner

Summary

  • Keep all six release-mode _build.yml target caches and all six release-binaries caches restorable, but stop saving new entries.
  • Extend the main-only cache-budget cleanup to retire only those 12 exact release-key families, alongside the already disabled all-features families. Unrelated preflight, coverage, musl, security, and Dylint caches remain outside the selector.
  • Document the measured 4,078,226,358-byte footprint and the tradeoff: future release target builds may start cold; release packaging/build/validation remain unchanged.

Closes #1216 after the main cache-budget workflow applies the reviewed cleanup and verifies a converged budget.

Validation

  • Focused cache-budget unit tests: 21 passed.
  • Cache-save-guard unit tests: 11 passed.
  • Cache save guard, Ruff, Black, YAML parse, and diff check passed.
  • Sole read-only clud-review: clean.

The repository has no ci-full label/contract; its broad exact-head PR matrix is the full platform gate.

@codecov

codecov Bot commented Sep 27, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ci(cache): rust-cache saves on pull requests — 13.4 GB of unreachable PR-ref caches over the 10 GB limit; add save-if and guard it

1 participant