Update eskatos/gradle-command-action action to v2 #555
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.
This PR contains the following updates:
v1.5.1
->v2.2.2
Release Notes
eskatos/gradle-command-action
v2.2.2
Compare Source
What's fixed
This release fixes some issues that were discovered in the
v2.2.1
release, and updates a number of dependencies.Full Changelog: gradle/gradle-build-action@v2.2.1...v2.2.2
v2.2.1
Compare Source
What's fixed
This release fixes some issues that were exposed by the
v2.2.0
release, as well as improving the content and layout of the Job Summary.Entry not saved: reason unknown
message in Job Summary cache details: #309Full Changelog: gradle/gradle-build-action@v2.2.0...v2.2.1
v2.2.0
Compare Source
Summary
This release brings a new Job Summary report, as well as numerous improvements and bug fixes:
cache-read-only
for non-default branches (see0a36ca9
)Issues resolved
https://github.com/gradle/gradle-build-action/milestone/7?closed=1
What's Changed
cache-read-only
for non-default branches by @bigdaz in https://github.com/gradle/gradle-build-action/pull/149Full Changelog: gradle/gradle-build-action@v2.1.7...v2.2.0
v2.1.7
Compare Source
Fixes #293, which prevented
v2.1.6
from allowing Gradle to re-use previously downloaded wrapper distributions. This slowed down build executions and could result in build flakiness when the wrapper zip failed to download.wrapper
folder of Gradle User Home, avoiding re-download of wrapper distributions.v2.1.6
Compare Source
This release contains an fix for changed behaviour in Gradle 7.6, as well as numerous library upgrades.
Earlier versions of the
gradle-build-action
were saving and restoring the downloaded Gradle wrapper zip file as part of caching the Gradle User Home. This will no longer work with Gradle 7.6, as the wrapper zip is now removed after expanding. This release ofgradle-build-action
contains a fix for this change in Gradle 7.6. Using an older version of the GitHub action with Gradle 7.6 will likely result in the wrapper being downloaded on every GitHub actions invocation.What's Changed
@actions/core
,@actions/cache
,@actions/github
,@actions/http-client
and@actions/tool-cache
.Full changelog: gradle/gradle-build-action@v2.1.5...v2.1.6
v2.1.5
Compare Source
This release addresses a potential security issue by upgrading
minimist
, and fixes a bug with very large cache entries by upgrading@actions/cache
. No other changes are included.What's Changed
Full changelog: gradle/gradle-build-action@v2.1.4...v2.1.5
v2.1.4
Compare Source
What's Changed
d700906
.Full Changelog: gradle/gradle-build-action@v2.1.3...v2.1.4
v2.1.3
Compare Source
This patch release fixes an issue that prevented the Gradle User Home from being restored from cache on
macos-latest
runners. #155What's Changed
Full Changelog: gradle/gradle-build-action@v2.1.2...v2.1.3
v2.1.2
Compare Source
This patch release fixes a minor bug and updates some NPM dependencies, including one dependency with a reported security advisory.
What's Changed
gradle.properties
is no longer overwritten by action initializationnode-fetch
to a version that isn't impacted by GHSA-r683-j2x4-v87g. Note that this CVE has been determined not to impact the action.Full Changelog: gradle/gradle-build-action@v2.1.1...v2.1.2
v2.1.1
Compare Source
This release improves logging and fixes a number of minor issues.
gradlew
script is not executable #76In addition, 2 experimental configuration parameters have been added:
gradle-home-cache-strict-match
: Only reuse cache entries generated by previous invocations for the same jobcache-write-only
: Do not restore cache entries but save on Job completionFull Changelog: gradle/gradle-build-action@v2.1.0...v2.1.1
v2.1.0
Compare Source
Overview
This release brings a major improvement in usability, allowing the action to be used to "setup Gradle" without requiring all Gradle invocations to be managed by the action.
Any Gradle invocation after the first
gradle-build-action
step will benefit from caching and build-scan capture just as if it was invoked through a subsequentgradle-build-action
. This is achieved viainit
scripts added when initializing/restoring the Gradle User Home.This change makes it easier to adopt the
gradle-build-action
into an existing GitHub Actions workflow and enables usages such as:Usability improvements
run
step to invoke Gradle and still benefit from Gradle User Home caching as well as build-scan integration.Caching improvements
Changes in detail
Full Changelog: gradle/gradle-build-action@v2.0.0...v2.1.0
v2.0.1
Compare Source
What's Changed
This patch release fixes a couple of cases where a failure to store caches would cause the entire Job to fail. The goal of the
gradle-build-action
is to warn-and-continue on all recoverable cache failures.Issues fixed
Full Changelog: gradle/gradle-build-action@v2.0.0...v2.0.1
v2.0.0
Compare Source
This is the initial release of
gradle-build-action@v2
, which brings significant performance and usability improvements overv1
. A few key improvements are outlined here, but see the project README for more details.Thanks for trying it out!
Usability improvements:
The
gradle-build-action
has been redesigned from the ground up to work well with minimal configuration, avoiding the need for most users to tweak multiple configuration options to benefit.Highlights:
Notice
annotations to your workflow run.Performance improvements:
A key benefit of
gradle-build-action
over other solutions is the sophisticated support for saving and restoring relevant Gradle state between build invocations. This caching support speeds up build invocations and is designed to work in most scenarios without further tweaking.Highlights:
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.