This is the first release of gradle/gradle-build-action
available with the v3
version tag.
Important
As of v3
this action has been superceded by gradle/actions/setup-gradle
.
Any workflow that uses gradle/gradle-build-action@v3
will transparently delegate to gradle/actions/setup-gradle@v3
.
Users are encouraged to update their workflows, replacing:
uses: gradle/gradle-build-action@v3
with
uses: gradle/actions/setup-gradle@v3
See the setup-gradle documentation for up-to-date documentation for gradle/actions/setup-gradle
.
Changes from gradle-build-action@v2
This 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 for gradle-build-action@v2
.
Changelog
- [NEW] - Run with NodeJs 20.x (#946)
- [NEW] - Support for save & restore of configuration-cache data (#966)
- [NEW] - Support for automatic adding PR comment with Job Summary content (#1020)
- [NEW] - Make it easy to publish a Build Scan® to https://scans.gradle.com (#1044)
- [NEW] - Added
dependency-graph-continue-on-failure
input, which can be set tofalse
to force the Job to fail when dependency graph submission fails (#1036). Failure modes include: - [NEW] - Add
dependency-graph: clear
option 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 (#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 (#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 (#995)
- [FIX] - Avoid submitting an empty dependency graph when state is loaded from configuration-cache
- [FIX] - Update to
GitHub Dependency Graph Gradle Plugin
v1.2.0 - [DEPRECATION] - Deprecation of the arguments parameter (#996)
- [BREAKING CHANGE] - Remove the
gradle-executable
input parameter. Use a separate workflow Step to execute a Gradle from a custom location.