MINOR: Revert setup-gradle action to v5.0.2 - #23240
Merged
Merged
Conversation
github-actions
Bot
added
triage
chia7712
pushed a commit
that referenced
this pull request
Aug 22, 2026
#22624 bumped setup-gradle from v5.0.2 to v6.2.0, because v5.0.2 had expired out of the ASF allowed actions list at the time. INFRA later added v5.0.2 back to the list and marked it `keep: true` so that it never expires, as v6 changes the licensing model of the default caching provider: apache/infrastructure-actions#953 This reverts to v5.0.2, which also avoids CI breaking again when the v6.2.0 pin expires on 2026-10-30. The 4.0, 4.1 and 4.2 branches already use v5.0.2, and the inputs of the action are unchanged. Reviewers: Chia-Ping Tsai <chia7712@gmail.com>
Member
|
cherry-picked to 4.4 branch |
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.
#22624 bumped setup-gradle from v5.0.2 to v6.2.0, because v5.0.2 had
expired out of the ASF allowed actions list at the time.
INFRA later added v5.0.2 back to the list and marked it
keep: truesothat it never expires, as v6 changes the licensing model of the default
caching provider:
apache/infrastructure-actions#953
This reverts to v5.0.2, which also avoids CI breaking again when the
v6.2.0 pin expires on 2026-10-30. The 4.0, 4.1 and 4.2 branches already
use v5.0.2, and the inputs of the action are unchanged.
Reviewers: Chia-Ping Tsai chia7712@gmail.com