⬆️ Bump gradle/gradle-build-action from 2 to 3
Bumps gradle/gradle-build-action from 2 to 3.
Release notes
Sourced from gradle/gradle-build-action's releases.
v3.0.0
This is the first release of
gradle/gradle-build-actionavailable with thev3version tag.[!IMPORTANT] As of
v3this action has been superceded bygradle/actions/setup-gradle. Any workflow that usesgradle/gradle-build-action@v3will transparently delegate togradle/actions/setup-gradle@v3.Users are encouraged to update their workflows, replacing:
uses: gradle/gradle-build-action@v3with
uses: gradle/actions/setup-gradle@v3See the setup-gradle documentation for up-to-date documentation for
gradle/actions/setup-gradle.Changes from
gradle-build-action@v2This release brings some useful and much requested features, including:
- save and restore the Gradle configuration-cache data
- add the Job summary content as a PR comment
- easily publish Build Scans® to the free Gradle Build Scan service
- compatibility with Node 20
The only major breaking change from
[email protected]is the update to require a Node 20 runtime environment. Aside from that change, this release should generally serve as a drop-in replacement forgradle-build-action@v2.Changelog
- [NEW] - Run with NodeJs 20.x (gradle/gradle-build-action#946)
- [NEW] - Support for save & restore of configuration-cache data (gradle/gradle-build-action#966)
- [NEW] - Support for automatic adding PR comment with Job Summary content (gradle/gradle-build-action#1020)
- [NEW] - Make it easy to publish a Build Scan® to https://scans.gradle.com (gradle/gradle-build-action#1044)
- [NEW] - Added
dependency-graph-continue-on-failureinput, which can be set tofalseto force the Job to fail when dependency graph submission fails (gradle/gradle-build-action#1036). Failure modes include:
- Fail build step if version of Gradle being executed is not supported for dependency-graph generation (gradle/gradle-build-action#1034)
- Fail job if permissions are insufficient to submit dependency graph via Dependency Submission API (gradle/gradle-build-action#997)
- [NEW] - Add
dependency-graph: clearoption to clear any dependency-graph previously submitted by the job- [FIX] Allow cache entries to be reused by jobs with the same ID in different workflows (gradle/gradle-build-action#1017)
- Workflow name remains part of the cache key, but cache entries generated by the same job id in a different workflow may be restored
- [FIX] Register pre-installed JDKs in Maven toolchains.xml file (gradle/gradle-build-action#1024)
- This allows pre-installed JDKs to be auto-detected by Gradle Toolchain support on Windows
- [FIX] - Update the Gradle Enterprise injection configuration for product rename to Develocity (gradle/gradle-build-action#995)
- [FIX] - Avoid submitting an empty dependency graph when state is loaded from configuration-cache
- [FIX] - Update to
GitHub Dependency Graph Gradle Pluginv1.2.0- [DEPRECATION] - Deprecation of the arguments parameter (gradle/gradle-build-action#996)
- [BREAKING CHANGE] - Remove the
gradle-executableinput parameter. Use a separate workflow Step to execute a Gradle from a custom location.
... (truncated)
Commits
66535aaBump to v3.4.204b20c0Bump to v3.4.1db35f23Bump to v3.4.04c39dd8Bump to v3.3.2e2097ccBump to use v3.3.18baac4cMap setup-gradle outputs back to gradle-build-action595fa85Run quick-check on mainf02f491Update action.yml for [email protected]cb6e43fEmit correct deprecation warnings in setup-gradlebdf99f9Update action.yml for v3.2.1- Additional commits viewable in compare view
Dependabot 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 mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@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)
Qodana Community for JVM
4 new problems were found
| Inspection name | Severity | Problems |
|---|---|---|
Boolean literal argument without parameter name |
◽️ Notice | 2 |
Return or assignment can be lifted out |
◽️ Notice | 1 |
Redundant lambda arrow |
◽️ Notice | 1 |
💡 Qodana analysis was run in the pull request mode: only the changed files were checked
View the detailed Qodana report
To be able to view the detailed Qodana report, you can either:
- Register at Qodana Cloud and configure the action
- Use GitHub Code Scanning with Qodana
- Host Qodana report at GitHub Pages
- Inspect and use
qodana.sarif.json(see the Qodana SARIF format for details)
To get *.log files or any other Qodana artifacts, run the action with upload-result option set to true,
so that the action will upload the files as the job artifacts:
- name: 'Qodana Scan'
uses: JetBrains/[email protected]
with:
upload-result: true
Contact Qodana team
Contact us at [email protected]
- Or via our issue tracker: https://jb.gg/qodana-issue
- Or share your feedback: https://jb.gg/qodana-discussions
@dependabot recreate
Looks like gradle/gradle-build-action is no longer a dependency, so this is no longer needed.