Bumps gradle/gradle-build-action from 2.12.0 to 3.0.0.
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
gradle-build-action@v2.12.0is 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
3b1b3b9Prepare for v3.0.0 released4bd442Delegate to 'setup-gradle@v3.0.0-rc.2'4587492Redirect some README contentef85c4eBump DV plugin version to 3.16.27e08fe2Run full-check on change to action.yml4a8703fDelegate to 'setup-gradle@v3.0.0-rc.1'4a39eedMention setup-gradle in README272883aRemove all action sources: these have been migrated to 'gradle/actions'2a8bfcfDelegate action implementation to gradle/actions/setup-gradlee1ada08Bump the github-actions group with 1 update (#1047)- 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 rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show
Comment From: dependabot[bot]
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.
If you change your mind, just re-open this PR and I'll resolve any conflicts on it.