Skip to content

ci: repin Swatinem/rust-cache to v2.9.3 - #603

Merged
vyncint merged 1 commit into
mainfrom
ci/repin-rust-cache-2.9.3
Oct 21, 2026
Merged

vyncint merged 1 commit into
mainfrom
ci/repin-rust-cache-2.9.3

Conversation

@vyncint

@vyncint vyncint commented Oct 21, 2026

Copy link
Copy Markdown
Owner

Upstream moved Swatinem/rust-cache's v2 tag from 6323deb (v2.9.2) to d1527c8 (v2.9.3) on 2026-10-20. zizmor's online ref-version-mismatch audit now fails on all six uses: ci.yml ×5 and stress.yml ×1. That makes zizmor, and so required-green, red on main (ea0f265) and on #601 and #602, with no change on our side.

This repins all six uses to d1527c8f67ef9af357290475d4af4b0fab8f12e0 # v2. I checked the SHA with gh api repos/Swatinem/rust-cache/commits/v2, and v2.9.3 points to the same commit. The upstream source diff is three small fixes:

  • missing awaits in the target cleanup;
  • timestamp-based pruning used to stop after the first entry;
  • a failed rustup toolchain list is now logged as info, not a warning.

The rest is a dependency bump and a rebuilt dist/.

Same shape as #554 and #567 for dtolnay/rust-toolchain.

Upstream moved the v2 tag from 6323deb (v2.9.2) to d1527c8 (v2.9.3) on
2026-10-20. zizmor's online ref-version-mismatch audit now fails on all
six uses, so the zizmor job, and required-green with it, is red on main
and on every pull request with no change on our side.

2.9.3 adds missing awaits in the target cleanup, fixes timestamp-based
pruning stopping after the first entry, and logs a failed `rustup
toolchain list` as info instead of a warning; the rest is a dependency
bump and a rebuilt dist.

Signed-off-by: Vyncint Ng <115854244+vyncint@users.noreply.github.com>
@vyncint
vyncint merged commit 018014c into main Oct 21, 2026
16 checks passed
@vyncint
vyncint deleted the ci/repin-rust-cache-2.9.3 branch October 21, 2026 23:59
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.

1 participant