chore(deps): bump gradle/actions from 5 to 6#74
Open
dependabot[bot] wants to merge 1 commit intodevfrom
Open
Conversation
Bumps [gradle/actions](https://github.com/gradle/actions) from 5 to 6. - [Release notes](https://github.com/gradle/actions/releases) - [Commits](gradle/actions@v5...v6) --- updated-dependencies: - dependency-name: gradle/actions dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
|
|
||
| - name: Set up Gradle | ||
| uses: gradle/actions/setup-gradle@v5 | ||
| uses: gradle/actions/setup-gradle@v6 |
There was a problem hiding this comment.
gradle/actions@v6 moves its caching logic into gradle-actions-caching, a proprietary component governed by separate Terms of Use (gradle.com/legal/terms-of-use). Because neither workflow explicitly sets cache-disabled: true, caching is on by default — meaning the proprietary component will be loaded and its license terms apply.
If the team agrees to those terms, this is fine as-is. If not, caching can be opted out of per step:
Suggested change
| uses: gradle/actions/setup-gradle@v6 | |
| uses: gradle/actions/setup-gradle@v6 | |
| with: | |
| cache-disabled: true |
The same consideration applies to Release.yaml line 33 and the dependency-submission step in CI.yaml (line 53). This is already noted in the PR description, so it's mainly worth an explicit team decision before merging.
Prompt To Fix With AI
This is a comment left during a code review.
Path: .github/workflows/CI.yaml
Line: 27
Comment:
**Proprietary caching component bundled in v6**
`gradle/actions@v6` moves its caching logic into `gradle-actions-caching`, a proprietary component governed by separate Terms of Use (gradle.com/legal/terms-of-use). Because neither workflow explicitly sets `cache-disabled: true`, caching is on by default — meaning the proprietary component will be loaded and its license terms apply.
If the team agrees to those terms, this is fine as-is. If not, caching can be opted out of per step:
```suggestion
uses: gradle/actions/setup-gradle@v6
with:
cache-disabled: true
```
The same consideration applies to `Release.yaml` line 33 and the `dependency-submission` step in `CI.yaml` (line 53). This is already noted in the PR description, so it's mainly worth an explicit team decision before merging.
How can I resolve this? If you propose a fix, please make it concise.
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
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.
Bumps gradle/actions from 5 to 6.
Release notes
Sourced from gradle/actions's releases.
... (truncated)
Commits
39e147c[bot] Update dist directory14ac3d6Bump com.fasterxml.jackson.dataformat:jackson-dataformat-smile from 2.21.1 to...81fec7aMention explicit license acceptance in notice (#912)4ac5b01[bot] Update dist directoryf64284cMute license warning when terms are accepted (#911)c2457a7Update tagging instructions for release8205114Update Gradle version compatibility information6710000Add typing information for use by typesafegithub (#910)3d0e2a8Pin version for github actionsf663ed9Ignore internal action files for type validationDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)Greptile Summary
This is a routine Dependabot bump of
gradle/actionsfrom v5 to v6 across both CI and Release workflows. The change is minimal and mechanically correct — all three usages (setup-gradlein CI and Release,dependency-submissionin CI) are consistently updated.\n\nThe one noteworthy aspect of this major-version bump is a licensing change: the caching functionality in v6 has been extracted intogradle-actions-caching, a proprietary bundled component under separate Terms of Use. Since neither workflow disables caching, the proprietary component will be active by default. The PR description already calls this out, so the team should make a deliberate decision to accept those terms before merging.\n\n-CI.yaml:setup-gradleanddependency-submissionboth updated v5 → v6\n-Release.yaml:setup-gradleupdated v5 → v6\n- v6 also removes configuration-cache support and updates internal npm dependencies to address security vulnerabilitiesConfidence Score: 4/5
Safe to merge once the team has consciously accepted the new gradle-actions-caching Terms of Use.
The code change itself is trivial and correct. The only consideration is a deliberate licensing decision that the PR description already surfaces. No functional regressions are expected.
No files require special technical attention; the licensing consideration spans all three action usages.
Important Files Changed
gradle/actions/setup-gradleandgradle/actions/dependency-submissionfrom v5 to v6; caching is now handled by a proprietary bundled component under separate Terms of Use.gradle/actions/setup-gradlefrom v5 to v6; same proprietary caching licensing consideration applies here.Flowchart
%%{init: {'theme': 'neutral'}}%% flowchart TD A[Push or PR to main] --> B[CI Workflow] R[GitHub Release published] --> C[Release Workflow] B --> D[checkout] D --> E[setup-java] E --> F[setup-gradle v6] F --> G{Caching enabled?} G -- yes --> H[gradle-actions-caching\nproprietary component] G -- no --> I[No caching] H --> J[gradlew build] I --> J J --> K[Publish SNAPSHOT\nif on main and SNAPSHOT version] K --> L[dependency-submission v6] C --> M[checkout] M --> N[setup-java] N --> O[setup-gradle v6] O --> P{Caching enabled?} P -- yes --> Q[gradle-actions-caching\nproprietary component] P -- no --> S[No caching] Q --> T[gradlew build and deploy] S --> TPrompt To Fix All With AI
Reviews (1): Last reviewed commit: "chore(deps): bump gradle/actions from 5 ..." | Re-trigger Greptile