gradle/gradle-build-action (gradle/gradle-build-action)
### [`v3.2.0`](https://togithub.com/gradle/gradle-build-action/compare/v3.1.0...v3.2.0)
[Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v3.1.0...v3.2.0)
### [`v3.1.0`](https://togithub.com/gradle/gradle-build-action/releases/tag/v3.1.0)
[Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v3.0.0...v3.1.0)
> \[!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](https://togithub.com/gradle/actions/tree/main/setup-gradle) for up-to-date documentation for `gradle/actions/setup-gradle`.
For release details, see https://github.com/gradle/actions/releases/tag/v3.1.0
### [`v3.0.0`](https://togithub.com/gradle/gradle-build-action/releases/tag/v3.0.0)
[Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.12.0...v3.0.0)
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](https://togithub.com/gradle/actions/tree/main/setup-gradle) 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](https://scans.gradle.com)
- compatibility with Node 20
The only major breaking change from `gradle-build-action@v2.12.0` 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 [https://github.com/gradle/gradle-build-action/issues/946](https://togithub.com/gradle/gradle-build-action/issues/946)6)
- \[NEW] - Support for save & restore of configuration-cache data [https://github.com/gradle/gradle-build-action/issues/966](https://togithub.com/gradle/gradle-build-action/issues/966)6)
- \[NEW] - Support for automatic adding PR comment with Job Summary content [https://github.com/gradle/gradle-build-action/issues/1020](https://togithub.com/gradle/gradle-build-action/issues/1020)0)
- \[NEW] - Make it easy to publish a Build Scan® to https://scans.gradle.com [https://github.com/gradle/gradle-build-action/issues/1044](https://togithub.com/gradle/gradle-build-action/issues/1044)4)
- \[NEW] - Added `dependency-graph-continue-on-failure` input, which can be set to `false` to force the Job to fail when dependency graph submission fails ([https://github.com/gradle/gradle-build-action/issues/1036](https://togithub.com/gradle/gradle-build-action/issues/1036)). Failure modes include:
- Fail build step if version of Gradle being executed is not supported for dependency-graph generation ([https://github.com/gradle/gradle-build-action/issues/1034](https://togithub.com/gradle/gradle-build-action/issues/1034))
- Fail job if permissions are insufficient to submit dependency graph via Dependency Submission API ([https://github.com/gradle/gradle-build-action/issues/997](https://togithub.com/gradle/gradle-build-action/issues/997))
- \[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 [https://github.com/gradle/gradle-build-action/issues/1017](https://togithub.com/gradle/gradle-build-action/issues/1017)7)
- 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 [https://github.com/gradle/gradle-build-action/issues/1024](https://togithub.com/gradle/gradle-build-action/issues/1024)4)
- 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 [https://github.com/gradle/gradle-build-action/issues/995](https://togithub.com/gradle/gradle-build-action/issues/995)5)
- \[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](https://togithub.com/gradle/github-dependency-graph-gradle-plugin/releases/tag/v1.2.0)
- \[DEPRECATION] - Deprecation of the arguments parameter [https://github.com/gradle/gradle-build-action/issues/996](https://togithub.com/gradle/gradle-build-action/issues/996)6)
- \[BREAKING CHANGE] - Remove the `gradle-executable` input parameter. Use a separate workflow Step to execute a Gradle from a custom location.
### [`v2.12.0`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.12.0)
[Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.11.1...v2.12.0)
Adds a new option to clear a previously submitted dependency-graph.
```yaml
steps:
- uses: gradle/gradle-build-action@v2
with:
dependency-graph: clear
```
This may prove useful when migrating to a workflow using the upcoming `gradle/actions/dependency-submission` action.
**Full-changelog**: https://github.com/gradle/gradle-build-action/compare/v2.11.1...v2.12.0
### [`v2.11.1`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.11.1)
[Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.11.0...v2.11.1)
This patch release fixes an issue that prevented the `gradle-build-action` from executing with Gradle 1.12, and improves error reporting for dependency submission failures.
##### Changelog
- \[FIX] Poor error reporting for dependency-submission failure [#1008](https://togithub.com/gradle/gradle-build-action/issues/1008)
- \[FIX] Error with gradle-build-action v2.11.0 and Gradle 1.12: unable to resolve class PluginManager [#1007](https://togithub.com/gradle/gradle-build-action/issues/1007)
**Full-changelog**: https://github.com/gradle/gradle-build-action/compare/v2.11.0...v2.11.1
### [`v2.11.0`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.11.0)
[Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.10.0...v2.11.0)
In addition to a number of dependency updates, this release:
- Allows a custom Plugin Repository to be specified when resolving the [github-dependency-graph-gradle-plugin](https://plugins.gradle.org/plugin/org.gradle.github-dependency-graph-gradle-plugin). See [the documentation](https://togithub.com/gradle/gradle-build-action#using-a-custom-plugin-repository) for details.
- Brings increased resilience when failures occur collecting build results or cleaning the Gradle User Home. Such failures should no longer prevent the caching of Gradle User Home or lead to build failures.
##### Changelog
- \[NEW] Allow a custom plugin repository to be used to resolve dependency-graph plugin [#933](https://togithub.com/gradle/gradle-build-action/issues/933)
- \[FIX] Cache entries and Job Summary not written on cache-cleanup failure [#990](https://togithub.com/gradle/gradle-build-action/issues/990) [#858](https://togithub.com/gradle/gradle-build-action/issues/858)
- \[FIX] Failure to write build results file should not cause overall build to fail [#866](https://togithub.com/gradle/gradle-build-action/issues/866)
**Full-changelog**: https://github.com/gradle/gradle-build-action/compare/v2.10.0...v2.11.0
### [`v2.10.0`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.10.0)
[Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.9.0...v2.10.0)
This release introduces a new `artifact-retention-days` parameter, which allows a user to configure how long the generated dependency-graph artifacts are retained by GitHub Actions. Adjusting the retention period can be useful to reduce storage costs associated with these dependency-graph artifacts.
See [the documentation](https://togithub.com/gradle/gradle-build-action/tree/v2.10.0#reducing-storage-costs-for-saved-dependency-graph-artifacts) for more details.
##### Changelog
- \[NEW] Add `artifact-retention-days` configuration parameter [#903](https://togithub.com/gradle/gradle-build-action/issues/903)
- \[FIX] Update to `v1.0.0` of the [github-dependency-graph-gradle-plugin](https://plugins.gradle.org/plugin/org.gradle.github-dependency-graph-gradle-plugin)
- \[FIX] Update `@babel/traverse` to address [reported security vulnerability](https://togithub.com/gradle/gradle-build-action/security/dependabot/18)
**Full-changelog**: https://github.com/gradle/gradle-build-action/compare/v2.9.0...v2.10.0
### [`v2.9.0`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.9.0)
[Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.8.1...v2.9.0)
The GitHub [dependency-review-action](https://togithub.com/actions/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](https://togithub.com/gradle/gradle-build-action#integrating-the-dependency-review-action) for detailed examples.
##### Changelog
- \[FIX] Use correct SHA for `pull-request` events [#882](https://togithub.com/gradle/gradle-build-action/issues/882)
- \[FIX] Avoid generating dependency graph during cache cleanup [#905](https://togithub.com/gradle/gradle-build-action/issues/905)
- \[NEW] Improve warning on failure to submit dependency graph
- \[NEW] Compatibility with GitHub `dependency-review-action` [#879](https://togithub.com/gradle/gradle-build-action/issues/879)
**Full-changelog**: https://github.com/gradle/gradle-build-action/compare/v2.8.1...v2.9.0
### [`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
### [`v2.6.0`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.6.0)
[Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.5.1...v2.6.0)
##### GitHub Dependency Graph support (Experimental)
This release brings experimental support for submitting a [GitHub Dependency Graph](https://docs.github.com/en/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph) snapshot via the [GitHub Dependency Submission API](https://docs.github.com/en/rest/dependency-graph/dependency-submission?apiVersion=2022-11-28).
The dependency graph snapshot is generated via integration with the [GitHub Dependency Graph Gradle Plugin](https://plugins.gradle.org/plugin/org.gradle.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](https://docs.github.com/en/code-security/dependabot/dependabot-alerts/about-dependabot-alerts) for vulnerable dependencies, as well as to populate the [Dependency Graph insights view](https://docs.github.com/en/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#viewing-the-dependency-graph).
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`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.5.1)
[Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.5.0...v2.5.1)
Fixes a regression in v2.5.0 that resulted in failure when running a workflow that has a name containing a comma.
##### Fixes
- Cache key Validation Error when workflow name contains a comma [#756](https://togithub.com/gradle/gradle-build-action/issues/756)
##### Changelog
### [`v2.5.0`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.5.0)
[Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.4.2...v2.5.0)
This minor release fixes a couple of issues that affected the action in particular scenarios, and updates all dependencies to recent versions.
##### Fixes
- Parallel workflows containing jobs with the same name use the same cache key [#699](https://togithub.com/gradle/gradle-build-action/issues/699)
- Build scans are not captured when GE plugin is applied within `settingsEvaluated` [#626](https://togithub.com/gradle/gradle-build-action/issues/626)
**Full changelog**: https://github.com/gradle/gradle-build-action/compare/v2.4.2...v2.5.0
Configuration
📅 Schedule: Branch creation - "on monday" (UTC), 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.4.2->v3.2.0Release Notes
gradle/gradle-build-action (gradle/gradle-build-action)
### [`v3.2.0`](https://togithub.com/gradle/gradle-build-action/compare/v3.1.0...v3.2.0) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v3.1.0...v3.2.0) ### [`v3.1.0`](https://togithub.com/gradle/gradle-build-action/releases/tag/v3.1.0) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v3.0.0...v3.1.0) > \[!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](https://togithub.com/gradle/actions/tree/main/setup-gradle) for up-to-date documentation for `gradle/actions/setup-gradle`. For release details, see https://github.com/gradle/actions/releases/tag/v3.1.0 ### [`v3.0.0`](https://togithub.com/gradle/gradle-build-action/releases/tag/v3.0.0) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.12.0...v3.0.0) 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](https://togithub.com/gradle/actions/tree/main/setup-gradle) 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](https://scans.gradle.com) - compatibility with Node 20 The only major breaking change from `gradle-build-action@v2.12.0` 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 [https://github.com/gradle/gradle-build-action/issues/946](https://togithub.com/gradle/gradle-build-action/issues/946)6) - \[NEW] - Support for save & restore of configuration-cache data [https://github.com/gradle/gradle-build-action/issues/966](https://togithub.com/gradle/gradle-build-action/issues/966)6) - \[NEW] - Support for automatic adding PR comment with Job Summary content [https://github.com/gradle/gradle-build-action/issues/1020](https://togithub.com/gradle/gradle-build-action/issues/1020)0) - \[NEW] - Make it easy to publish a Build Scan® to https://scans.gradle.com [https://github.com/gradle/gradle-build-action/issues/1044](https://togithub.com/gradle/gradle-build-action/issues/1044)4) - \[NEW] - Added `dependency-graph-continue-on-failure` input, which can be set to `false` to force the Job to fail when dependency graph submission fails ([https://github.com/gradle/gradle-build-action/issues/1036](https://togithub.com/gradle/gradle-build-action/issues/1036)). Failure modes include: - Fail build step if version of Gradle being executed is not supported for dependency-graph generation ([https://github.com/gradle/gradle-build-action/issues/1034](https://togithub.com/gradle/gradle-build-action/issues/1034)) - Fail job if permissions are insufficient to submit dependency graph via Dependency Submission API ([https://github.com/gradle/gradle-build-action/issues/997](https://togithub.com/gradle/gradle-build-action/issues/997)) - \[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 [https://github.com/gradle/gradle-build-action/issues/1017](https://togithub.com/gradle/gradle-build-action/issues/1017)7) - 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 [https://github.com/gradle/gradle-build-action/issues/1024](https://togithub.com/gradle/gradle-build-action/issues/1024)4) - 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 [https://github.com/gradle/gradle-build-action/issues/995](https://togithub.com/gradle/gradle-build-action/issues/995)5) - \[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](https://togithub.com/gradle/github-dependency-graph-gradle-plugin/releases/tag/v1.2.0) - \[DEPRECATION] - Deprecation of the arguments parameter [https://github.com/gradle/gradle-build-action/issues/996](https://togithub.com/gradle/gradle-build-action/issues/996)6) - \[BREAKING CHANGE] - Remove the `gradle-executable` input parameter. Use a separate workflow Step to execute a Gradle from a custom location. ### [`v2.12.0`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.12.0) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.11.1...v2.12.0) Adds a new option to clear a previously submitted dependency-graph. ```yaml steps: - uses: gradle/gradle-build-action@v2 with: dependency-graph: clear ``` This may prove useful when migrating to a workflow using the upcoming `gradle/actions/dependency-submission` action. **Full-changelog**: https://github.com/gradle/gradle-build-action/compare/v2.11.1...v2.12.0 ### [`v2.11.1`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.11.1) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.11.0...v2.11.1) This patch release fixes an issue that prevented the `gradle-build-action` from executing with Gradle 1.12, and improves error reporting for dependency submission failures. ##### Changelog - \[FIX] Poor error reporting for dependency-submission failure [#1008](https://togithub.com/gradle/gradle-build-action/issues/1008) - \[FIX] Error with gradle-build-action v2.11.0 and Gradle 1.12: unable to resolve class PluginManager [#1007](https://togithub.com/gradle/gradle-build-action/issues/1007) **Full-changelog**: https://github.com/gradle/gradle-build-action/compare/v2.11.0...v2.11.1 ### [`v2.11.0`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.11.0) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.10.0...v2.11.0) In addition to a number of dependency updates, this release: - Allows a custom Plugin Repository to be specified when resolving the [github-dependency-graph-gradle-plugin](https://plugins.gradle.org/plugin/org.gradle.github-dependency-graph-gradle-plugin). See [the documentation](https://togithub.com/gradle/gradle-build-action#using-a-custom-plugin-repository) for details. - Brings increased resilience when failures occur collecting build results or cleaning the Gradle User Home. Such failures should no longer prevent the caching of Gradle User Home or lead to build failures. ##### Changelog - \[NEW] Allow a custom plugin repository to be used to resolve dependency-graph plugin [#933](https://togithub.com/gradle/gradle-build-action/issues/933) - \[FIX] Cache entries and Job Summary not written on cache-cleanup failure [#990](https://togithub.com/gradle/gradle-build-action/issues/990) [#858](https://togithub.com/gradle/gradle-build-action/issues/858) - \[FIX] Failure to write build results file should not cause overall build to fail [#866](https://togithub.com/gradle/gradle-build-action/issues/866) **Full-changelog**: https://github.com/gradle/gradle-build-action/compare/v2.10.0...v2.11.0 ### [`v2.10.0`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.10.0) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.9.0...v2.10.0) This release introduces a new `artifact-retention-days` parameter, which allows a user to configure how long the generated dependency-graph artifacts are retained by GitHub Actions. Adjusting the retention period can be useful to reduce storage costs associated with these dependency-graph artifacts. See [the documentation](https://togithub.com/gradle/gradle-build-action/tree/v2.10.0#reducing-storage-costs-for-saved-dependency-graph-artifacts) for more details. ##### Changelog - \[NEW] Add `artifact-retention-days` configuration parameter [#903](https://togithub.com/gradle/gradle-build-action/issues/903) - \[FIX] Update to `v1.0.0` of the [github-dependency-graph-gradle-plugin](https://plugins.gradle.org/plugin/org.gradle.github-dependency-graph-gradle-plugin) - \[FIX] Update `@babel/traverse` to address [reported security vulnerability](https://togithub.com/gradle/gradle-build-action/security/dependabot/18) **Full-changelog**: https://github.com/gradle/gradle-build-action/compare/v2.9.0...v2.10.0 ### [`v2.9.0`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.9.0) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.8.1...v2.9.0) The GitHub [dependency-review-action](https://togithub.com/actions/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](https://togithub.com/gradle/gradle-build-action#integrating-the-dependency-review-action) for detailed examples. ##### Changelog - \[FIX] Use correct SHA for `pull-request` events [#882](https://togithub.com/gradle/gradle-build-action/issues/882) - \[FIX] Avoid generating dependency graph during cache cleanup [#905](https://togithub.com/gradle/gradle-build-action/issues/905) - \[NEW] Improve warning on failure to submit dependency graph - \[NEW] Compatibility with GitHub `dependency-review-action` [#879](https://togithub.com/gradle/gradle-build-action/issues/879) **Full-changelog**: https://github.com/gradle/gradle-build-action/compare/v2.8.1...v2.9.0 ### [`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 ### [`v2.6.0`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.6.0) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.5.1...v2.6.0) ##### GitHub Dependency Graph support (Experimental) This release brings experimental support for submitting a [GitHub Dependency Graph](https://docs.github.com/en/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph) snapshot via the [GitHub Dependency Submission API](https://docs.github.com/en/rest/dependency-graph/dependency-submission?apiVersion=2022-11-28). The dependency graph snapshot is generated via integration with the [GitHub Dependency Graph Gradle Plugin](https://plugins.gradle.org/plugin/org.gradle.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](https://docs.github.com/en/code-security/dependabot/dependabot-alerts/about-dependabot-alerts) for vulnerable dependencies, as well as to populate the [Dependency Graph insights view](https://docs.github.com/en/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#viewing-the-dependency-graph). 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`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.5.1) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.5.0...v2.5.1) Fixes a regression in v2.5.0 that resulted in failure when running a workflow that has a name containing a comma. ##### Fixes - Cache key Validation Error when workflow name contains a comma [#756](https://togithub.com/gradle/gradle-build-action/issues/756) ##### Changelog ### [`v2.5.0`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.5.0) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.4.2...v2.5.0) This minor release fixes a couple of issues that affected the action in particular scenarios, and updates all dependencies to recent versions. ##### Fixes - Parallel workflows containing jobs with the same name use the same cache key [#699](https://togithub.com/gradle/gradle-build-action/issues/699) - Build scans are not captured when GE plugin is applied within `settingsEvaluated` [#626](https://togithub.com/gradle/gradle-build-action/issues/626) **Full changelog**: https://github.com/gradle/gradle-build-action/compare/v2.4.2...v2.5.0Configuration
📅 Schedule: Branch creation - "on monday" (UTC), 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.