gradle/gradle-build-action (gradle/gradle-build-action)
### [`v2.8.1`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.8.1)
[Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.8.0...v2.8.1)
Fixes an issue that prevented Dependency Graph submission when running on GitHub Enterprise Server.
##### Fixes
- Incorrect endpoint used to submit Dependency Graph on GitHub Enterprise [#885](https://togithub.com/gradle/gradle-build-action/issues/885)
##### Changelog
### [`v2.8.0`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.8.0)
[Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.7.1...v2.8.0)
The `v2.8.0` release of the `gradle-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](https://togithub.com/gradle/gradle-build-action/blob/v2.8.0/README.md#gradle-enterprise-plugin-injection) 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:
- The Job Summary now includes a useful error message when Gradle User Home was not restored because the directory already exists.
- The action can now be configured to restore the Gradle User Home when the directory already exists, overwriting existing content with content from the GitHub Actions cache. See https://github.com/gradle/gradle-build-action#overwriting-an-existing-gradle-user-home for more details.
##### Changes
**Issues fixed**: https://github.com/gradle/gradle-build-action/issues?q=milestone%3A2.8.0+is%3Aclosed
**Full changelog**: https://github.com/gradle/gradle-build-action/compare/v2.7.1...v2.8.0
### [`v2.7.1`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.7.1)
[Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.7.0...v2.7.1)
This release contains no code changes, only dependency updates and documentation improvements.
##### Changelog
### [`v2.7.0`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.7.0)
[Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.6.1...v2.7.0)
#### 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](https://togithub.com/gradle/gradle-build-action#github-dependency-graph-support).
##### Changes
- Update to [`github-dependency-graph-gradle-plugin@v0.2.0`](https://plugins.gradle.org/plugin/org.gradle.github-dependency-graph-gradle-plugin/0.2.0)
- Dependency graph uses Gradle Settings file as manifest location (if Settings file exists)
- Adds a `dependency-graph-file` output to any step that generates a Dependency Graph file
##### Changelog
### [`v2.6.1`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.6.1)
[Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.6.0...v2.6.1)
##### Dependency Graph support
This patch release fixes and improves a couple of aspects of the experimental Dependency Graph support:
- The action will now generate a unique `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.
- Update to use [`github-dependency-graph-gradle-plugin@v0.1.0`](https://plugins.gradle.org/plugin/org.gradle.github-dependency-graph-gradle-plugin), which brings a number of improvements to the generated dependency graph:
- Each Gradle build invocation is mapped to a single GitHub Dependency Graph manifest. This should result in fewer duplicate security alerts being generated.
- Configurations that contribute to the GitHub Dependency Graph can be filtered by regular expression
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.
[ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.
This PR contains the following updates:
v2.6.0->v2.8.1Release Notes
gradle/gradle-build-action (gradle/gradle-build-action)
### [`v2.8.1`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.8.1) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.8.0...v2.8.1) Fixes an issue that prevented Dependency Graph submission when running on GitHub Enterprise Server. ##### Fixes - Incorrect endpoint used to submit Dependency Graph on GitHub Enterprise [#885](https://togithub.com/gradle/gradle-build-action/issues/885) ##### Changelog ### [`v2.8.0`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.8.0) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.7.1...v2.8.0) The `v2.8.0` release of the `gradle-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](https://togithub.com/gradle/gradle-build-action/blob/v2.8.0/README.md#gradle-enterprise-plugin-injection) 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: - The Job Summary now includes a useful error message when Gradle User Home was not restored because the directory already exists. - The action can now be configured to restore the Gradle User Home when the directory already exists, overwriting existing content with content from the GitHub Actions cache. See https://github.com/gradle/gradle-build-action#overwriting-an-existing-gradle-user-home for more details. ##### Changes **Issues fixed**: https://github.com/gradle/gradle-build-action/issues?q=milestone%3A2.8.0+is%3Aclosed **Full changelog**: https://github.com/gradle/gradle-build-action/compare/v2.7.1...v2.8.0 ### [`v2.7.1`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.7.1) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.7.0...v2.7.1) This release contains no code changes, only dependency updates and documentation improvements. ##### Changelog ### [`v2.7.0`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.7.0) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.6.1...v2.7.0) #### 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](https://togithub.com/gradle/gradle-build-action#github-dependency-graph-support). ##### Changes - Update to [`github-dependency-graph-gradle-plugin@v0.2.0`](https://plugins.gradle.org/plugin/org.gradle.github-dependency-graph-gradle-plugin/0.2.0) - Dependency graph uses Gradle Settings file as manifest location (if Settings file exists) - Adds a `dependency-graph-file` output to any step that generates a Dependency Graph file ##### Changelog ### [`v2.6.1`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.6.1) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.6.0...v2.6.1) ##### Dependency Graph support This patch release fixes and improves a couple of aspects of the experimental Dependency Graph support: - The action will now generate a unique `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. - Update to use [`github-dependency-graph-gradle-plugin@v0.1.0`](https://plugins.gradle.org/plugin/org.gradle.github-dependency-graph-gradle-plugin), which brings a number of improvements to the generated dependency graph: - Each Gradle build invocation is mapped to a single GitHub Dependency Graph manifest. This should result in fewer duplicate security alerts being generated. - Configurations that contribute to the GitHub Dependency Graph can be filtered by regular expressionConfiguration
📅 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.