#3885: Upgrade GitHub Actions to latest versions
Cluster:
GitHub Actions CI Improvements
## Summary
Upgrade GitHub Actions to their latest versions for improved features, bug fixes, and security updates.
## Changes
| Action | Old Version(s) | New Version | Release | Files |
|--------|---------------|-------------|---------|-------|
| `actions/create-github-app-token` | [`v1`](https://github.com/actions/create-github-app-token/releases/tag/v1) | [`v2`](https://github.com/actions/create-github-app-token/releases/tag/v2) | [Release](https://github.com/actions/create-github-app-token/releases/tag/v2) | auto-response.yml, labeler.yml |
| `gradle/actions/setup-gradle` | [`v4`](https://github.com/gradle/actions/setup-gradle/releases/tag/v4) | [`v5`](https://github.com/gradle/actions/setup-gradle/releases/tag/v5) | [Release](https://github.com/gradle/actions/setup-gradle/releases/tag/v5) | ci.yml |
## Why upgrade?
Keeping GitHub Actions up to date ensures:
- **Security**: Latest security patches and fixes
- **Features**: Access to new functionality and improvements
- **Compatibility**: Better support for current GitHub features
- **Performance**: Optimizations and efficiency improvements
### Security Note
Actions that were previously pinned to commit SHAs remain pinned to SHAs (updated to the latest release SHA) to maintain the security benefits of immutable references.
### Testing
These changes only affect CI/CD workflow configurations and should not impact application functionality. The workflows should be tested by running them on a branch before merging.
<!-- greptile_comment -->
<h2>Greptile Overview</h2>
<h3>Greptile Summary</h3>
This PR updates GitHub Actions versions in the repository’s workflows: `actions/create-github-app-token` is bumped from `v1` to `v2` in the `auto-response` and `labeler` workflows, and `gradle/actions/setup-gradle` is bumped from `v4` to `v5` in the Android portion of the main CI workflow. These changes are confined to `.github/workflows/*` and primarily affect how the workflows authenticate and set up Gradle during CI runs.
<h3>Confidence Score: 4/5</h3>
- This PR is likely safe to merge; changes are limited to GitHub Actions version bumps, with one security hardening mismatch to double-check.
- The diffs are small and localized to workflow `uses:` lines. The main risk is behavioral changes in major-version upgrades (notably `create-github-app-token@v2`) and the PR’s stated intent to pin actions to SHAs not being reflected in the actual workflow changes, which could affect supply-chain hardening expectations.
- .github/workflows/auto-response.yml, .github/workflows/labeler.yml
<!-- greptile_other_comments_section -->
<!-- /greptile_comment -->
Most Similar PRs
#3884: Upgrade GitHub Actions for Node 24 compatibility
by salmanmkc · 2026-01-29
86.0%
#9474: fix: GitHub Actions not pinned to SHA digests in CI/CD workflows
by coygeek · 2026-02-05
81.3%
#11765: fix(ci): restrict GITHUB_TOKEN permissions in workflows
by coygeek · 2026-02-08
76.5%
#11048: fix: address repository issues (env, author, CI comments, security ...
by cavula · 2026-02-07
75.9%
#22250: ci: pin GitHub Actions to SHA and harden Dockerfiles
by novalis133 · 2026-02-20
75.5%
#11313: feat(ci): add staged release pipeline workflows (dormant)
by quotentiroler · 2026-02-07
74.7%
#22580: CI: pin workflow action refs to immutable SHAs
by Rohan5commit · 2026-02-21
73.5%
#4432: docs: update molt.bot links in auto response
by felirami · 2026-01-30
73.0%
#17452: ci: Grant write perms for Issues for formal-conformance.yml
by thesomewhatyou · 2026-02-15
73.0%
#12396: chore(deps): improve dependabot configuration with commit message p...
by dikshithreddym · 2026-02-09
71.9%