Update gradle/gradle-build-action action to v2.9.0 #4
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:
v2.4.2
->v2.9.0
Release Notes
gradle/gradle-build-action (gradle/gradle-build-action)
v2.9.0
Compare Source
The GitHub dependency-review-action helps you understand dependency changes (and the security impact of these changes) for a pull request. This release updates the GItHub Dependency Graph support to be compatible with the
dependency-review-action
.See the documentation for detailed examples.
Changelog
pull-request
events #882dependency-review-action
#879Full-changelog: gradle/gradle-build-action@v2.8.1...v2.9.0
v2.8.1
Compare Source
Fixes an issue that prevented Dependency Graph submission when running on GitHub Enterprise Server.
Fixes
Changelog
v2.8.0
Compare Source
The
v2.8.0
release of thegradle-build-action
introduces an easy mechanism to connect to Gradle Enterprise, as well improved support for self-hosted GitHub Actions runners.Automatic injection of Gradle Enterprise connectivity
It is now possible to connect a Gradle build to Gradle Enterprise without changing any of the Gradle project sources. This is achieved through Gradle Enterprise injection, where an init-script will apply the Gradle Enterprise plugin and associated configuration.
This feature can be useful to easily trial Gradle Enterprise on a project, or to centralize Gradle Enterprise configuration for all GitHub Actions workflows in an organization.
See Gradle Enterprise injection in the README for more info.
Restore Gradle User Home when directory already exists
Previously, the Gradle User Home would not be restored if the directory already exists. This wasn't normally an issue with GitHub-hosted runners, but limited the usefulness of the action for persistent, self-hosted runners.
This behaviour has been improved in this release:
Changes
Issues fixed: https://github.com/gradle/gradle-build-action/issues?q=milestone%3A2.8.0+is%3Aclosed
Full changelog: gradle/gradle-build-action@v2.7.1...v2.8.0
v2.7.1
Compare Source
This release contains no code changes, only dependency updates and documentation improvements.
Changelog
v2.7.0
Compare Source
GitHub Dependency Graph support
In this release, the GitHub Dependency Graph support is no longer considered "experimental", and should be considered ready for production use. You can read more about the Dependency Graph support in the README chapter.
Changes
[email protected]
dependency-graph-file
output to any step that generates a Dependency Graph fileChangelog
v2.6.1
Compare Source
Dependency Graph support
This patch release fixes and improves a couple of aspects of the experimental Dependency Graph support:
job.correlator
value for each Gradle invocation within a Job. This permits multiple Gradle invocations in a single job to generate and submit a separate dependency graph.[email protected]
, which brings a number of improvements to the generated dependency graph:v2.6.0
Compare Source
GitHub Dependency Graph support (Experimental)
This release brings experimental support for submitting a GitHub Dependency Graph snapshot via the GitHub Dependency Submission API.
The dependency graph snapshot is generated via integration with the GitHub Dependency Graph Gradle Plugin, and saved as a workflow artifact. The generated snapshot files can be submitted either in the same job, or in a subsequent job (in the same or a dependent workflow).
The generated dependency graph snapshot reports all of the dependencies that were resolved during a bulid execution, and is used by GitHub to generate Dependabot Alerts for vulnerable dependencies, as well as to populate the Dependency Graph insights view.
Check out the README chapter for more details on how this works and how to configure a workflow that submits a dependency graph.
Changelog
v2.5.1
Compare Source
Fixes a regression in v2.5.0 that resulted in failure when running a workflow that has a name containing a comma.
Fixes
Changelog
v2.5.0
Compare Source
This minor release fixes a couple of issues that affected the action in particular scenarios, and updates all dependencies to recent versions.
Fixes
settingsEvaluated
#626Full changelog: gradle/gradle-build-action@v2.4.2...v2.5.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.