chore(ci): bump GitHub Actions to latest versions - #5172
Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
ApprovabilityVerdict: Approved 75f54c1 Mechanical version bumps of GitHub Actions across workflow files (checkout, github-script, download-artifact, expo-github-action, etc.). No changes to workflow logic or deployment behavior - purely dependency version updates. You can customize Macroscope's approvability policy. Learn more. |
What Changed
Bumped every GitHub Action in
.github/workflows/to the latest major version.actions/checkoutv6(andv4in pr-size)v7actions/github-scriptv8(andv7in issue-labels)v9actions/download-artifactv7(one step in release)v8actions/create-github-app-tokenv2v3softprops/action-gh-releasev2v3expo/expo-github-actionv8(+continuous-deploy-fingerprint@main)v9gradle/actions/setup-gradlev5v6Actions already on the latest major were left alone (
setup-vp@v1,rust-toolchain@stable,upload-artifact@v7,vouch@v1,setup-java@v5,android-emulator-runner@v2). Theexpofingerprint sub-action is now pinned to the releasedv9tag instead of@main.Why
A sweep of open and closed PRs found no update of the GitHub Actions to their latest versions, so CI/CD has drifted behind upstream releases. Kept scope tight: no workflow logic changes, only version pins.
Compatibility checked before bumping:
github-script@v9breaksrequire('@actions/github'); no workflow script uses it.action-gh-release@v3,create-github-app-token@v3,expo-github-action@v9).checkout@v7's saferpull_request_targetdefault is safe here — the pr-size label job only checks out the base repo.UI Changes
N/A — CI-only changes.
Checklist
Note:
gradle/actions/setup-gradle@v6moves the caching component to Gradle's proprietarygradle-actions-cachinglibrary (MIT only when caching is disabled) — flagging in case that's a blocker; it only affects the manual screenshot workflow.