ci: bump hendrikmuhs/ccache-action from v1.2.23 to v1.2.24 - #459
Merged
Conversation
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UkvgWR9HfXtivLqo3ji2zd
kraenhansen
added
Apple 🍎
Claude
…e-api) Labels were added after the PR was already opened, so no synchronize event fired to re-evaluate the label-gated job conditions in check.yml. This empty commit forces that re-evaluation so the platform test jobs that exercise hendrikmuhs/ccache-action actually run before merge. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UkvgWR9HfXtivLqo3ji2zd
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
2 participants
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
Scheduled audit of every GitHub Action used across
.github/workflows/check.ymland.github/workflows/release.ymlagainst its latest available release (following up on #456, which handledactions/setup-java).hendrikmuhs/ccache-actionwas pinned to an exact patch,v1.2.23, per the comment above its first usage incheck.yml. That comment documents why an exact pin is used instead of the floatingv1/v1.2tags (they still resolve to a Node.js 20-based build) and says to float again once upstream moves them to>= v1.2.22. I confirmed via each tag'saction.ymlthat:v1andv1.2(floating) still declareusing: "node20"— the gate has not been unblocked, so the documented reason still holds and the exact-pin approach stays.v1.2.24(published afterv1.2.23, and after this pin was last verified) declaresusing: "node24", same asv1.2.23.So the only actionable gap is that
v1.2.24is now the latest exact tag andv1.2.23isn't, with no reason to stay behind.Change
Bumps all 8 occurrences of
hendrikmuhs/ccache-action(7 incheck.yml, 1 inrelease.yml) from@v1.2.23to@v1.2.24, keeping every usage at the same version. No comment changes — the existing rationale for the exact pin is still accurate.Every other action in these workflows (
actions/checkout@v7,actions/setup-node@v7,pnpm/action-setup@v6,aminya/setup-cpp@v1,android-actions/setup-android@v4,actions/upload-artifact@v7,reactivecircus/android-emulator-runner@v2,changesets/action/*@v2) is pinned to a floating major tag that already tracks the latest release in that line — no changes needed there.actions/setup-java@v5→@v6is already covered by open PR #456.🤖 Generated with Claude Code
https://claude.ai/code/session_01UkvgWR9HfXtivLqo3ji2zd
Generated by Claude Code