search

stempler / bnd-platform

Build OSGi bundles and Eclipse Update Sites from existing JARs, e.g. from Maven repositories (Plugin for Gradle)
Apache License 2.0
79 stars 30 forks source link

chore(deps): update gradle/gradle-build-action action to v3 - autoclosed #88

Closed renovate[bot] closed 6 months ago

renovate[bot] commented 6 months ago

Mend Renovate

This PR contains the following updates:

Package Type Update Change OpenSSF
gradle/gradle-build-action action major v2 -> v3.1.0 OpenSSF Scorecard

Release Notes

gradle/gradle-build-action (gradle/gradle-build-action) ### [`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 ### [`v2.4.2`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.4.2) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.4.1...v2.4.2) This release disables the save/restore of configuration-cache data, since this functionality has been shown to be problematic. Gradle 8.1 has made changes to this functionality which will require a more comprehensive rework of the action before we can re-enable this. ### [`v2.4.1`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.4.1) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.4.0...v2.4.1) This patch release updates a number of dependencies, including `xmljs` which was reported to have a security vulnerability (https://nvd.nist.gov/vuln/detail/CVE-2023-0842). There is no evidence that this vulnerability affected the `gradle-build-action`. **Full changelog**: https://github.com/gradle/gradle-build-action/compare/v2.4.0...v2.4.1 ### [`v2.4.0`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.4.0) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.3.3...v2.4.0) #### What's new The `v.2.4.0` release contains various library updates and fixes to fully support Gradle 8. Notable changes: - Update to `@actions/cache: 3.1.3` should improve cache save/restore performance on Windows by using gnu tar and zstd when available. - Fix caching of extracted JDK toolchains for Gradle 7.6+ ([`e444647`](https://togithub.com/gradle/gradle-build-action/commit/e4446473950007d0d0323adeed9f992824618be9)) **Full Changelog**: https://github.com/gradle/gradle-build-action/compare/v2.3.3...v2.4.0 ### [`v2.3.3`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.3.3) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.3.2...v2.3.3) This patch release removes all uses of the deprecated `set-output` and `set-state` commands, and should remove deprecation warnings from build logs. See [#​461](https://togithub.com/gradle/gradle-build-action/issues/461) and [#​477](https://togithub.com/gradle/gradle-build-action/issues/477) for more details. **Full Changelog**: https://github.com/gradle/gradle-build-action/compare/v2.3.2...v2.3.3 ### [`v2.3.2`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.3.2) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.3.1...v2.3.2) This patch release fixes an issue which could result in errors in the post-action step. See [#​441](https://togithub.com/gradle/gradle-build-action/issues/441) for details. **Full Changelog**: https://github.com/gradle/gradle-build-action/compare/v2.3.1...v2.3.2 ### [`v2.3.1`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.3.1) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.3.0...v2.3.1) This patch release addresses some security vulnerabilities reported by the CodeQL check: - Removes `sourcemap-register.js`: this triggered [Incorrect suffix check](https://togithub.com/gradle/gradle-build-action/security/code-scanning/3) - Patches the `@azure/logger` library to avoid logging an environment variable value: this triggered [Clear-text logging of sensitive information](https://togithub.com/gradle/gradle-build-action/security/code-scanning/8) - Updates a bunch of development dependencies, which should not impact production code The release contains no functional changes. **Full Changelog**: https://github.com/gradle/gradle-build-action/compare/v2.3.0...v2.3.1 ### [`v2.3.0`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.3.0) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.2.5...v2.3.0) #### What's new With `v2.3.0`, the `gradle-build-action` can now attempt to remove any unused files from the Gradle User Home directory before storing to the GitHub Actions cache. This can prevent cases where the size of cache entry grows over time. Gradle Home cache cleanup is disabled by default. You can enable this feature for the action as follows: ```yaml gradle-home-cache-cleanup: true ``` See [the README](https://togithub.com/gradle/gradle-build-action/blob/main/README.md#removing-unused-files-from-gradle-user-home-before-saving-to-cache) for more details. **Full Changelog**: https://github.com/gradle/gradle-build-action/compare/v2.2.5...v2.3.0 ### [`v2.2.5`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.2.5) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.2.4...v2.2.5) #### What's fixed Fixes a bug where a corrupted cache entry caused an error in `beforeSave` ([#​408](https://togithub.com/gradle/gradle-build-action/issues/408)). This meant that the entry was never purged. By allowing `@actions/globber` to follow symlinks and ignore broken symlinks, the bad files in the cache entry are ignored and the corrupted cache entry can be replaced by a good one. **Full Changelog**: https://github.com/gradle/gradle-build-action/compare/v2.2.4...v2.2.5 ### [`v2.2.4`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.2.4) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.2.3...v2.2.4) #### What's fixed The fix for [#​383](https://togithub.com/gradle/gradle-build-action/issues/383) introduced a bug that caused the post-action to fail when attempting to resolve cache-read-only for scheduled jobs. This has been fixed with an explicit (rather than implicit) check for 'event.repository != null'. ([#​409](https://togithub.com/gradle/gradle-build-action/issues/409)) **Full Changelog**: https://github.com/gradle/gradle-build-action/compare/v2.2.3...v2.2.4 ### [`v2.2.3`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.2.3) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.2.2...v2.2.3) #### What's fixed This release updates a number of key dependencies and fixes some cache-related issues: - Do not set `cache-read-only=true` for scheduled workflows on default branch ([#​383](https://togithub.com/gradle/gradle-build-action/issues/383)) - Fix reporting of caching errors that was broken in `v2.2.2` ([#​407](https://togithub.com/gradle/gradle-build-action/issues/407)) - Abort cache download operations after 10 minutes (configurable). Previously cache download operations could hang the build. ([#​369](https://togithub.com/gradle/gradle-build-action/issues/369)) **Full Changelog**: https://github.com/gradle/gradle-build-action/compare/v2.2.2...v2.2.3 ### [`v2.2.2`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.2.2) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.2.1...v2.2.2) #### What's fixed This release fixes some issues that were discovered in the `v2.2.1` release, and updates a number of dependencies. - Improved support for GitHub Enterprise - Do not attempt to use GitHub Actions cache when the feature is not available - Write Gradle Build summary to log files when Job Summary functionality not available - Only attempt to stop Gradle daemons when caching Gradle User Home ([#​341](https://togithub.com/gradle/gradle-build-action/issues/341)) - Only write build-results file when GitHub Actions env vars are available ([#​350](https://togithub.com/gradle/gradle-build-action/issues/350)) **Full Changelog**: https://github.com/gradle/gradle-build-action/compare/v2.2.1...v2.2.2 ### [`v2.2.1`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.2.1) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.2.0...v2.2.1) #### 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. - Don't try to generate Job Summary when functionality is not available (GitHub Enterprise): [#​319](https://togithub.com/gradle/gradle-build-action/issues/319) - Fix warning when attempting to delete non-existent file: [#​308](https://togithub.com/gradle/gradle-build-action/issues/308) - Fix `Entry not saved: reason unknown` message in Job Summary cache details: [#​309](https://togithub.com/gradle/gradle-build-action/issues/309) - Report failure to publish build scan in Job Summary: [#​326](https://togithub.com/gradle/gradle-build-action/issues/326) **Full Changelog**: https://github.com/gradle/gradle-build-action/compare/v2.2.0...v2.2.1 ### [`v2.2.0`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.2.0) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.1.7...v2.2.0) #### Summary This release brings a new Job Summary report, as well as numerous improvements and bug fixes: - Capture all Gradle build executions for a job and write them to the GitHub Actions Job Summary. - Default to `cache-read-only` for non-default branches (see [`0a36ca9`](https://togithub.com/gradle/gradle-build-action/commit/0a36ca9fb8a7acc820f34da9116f389a13dc67e2)) - Allow the Gradle Daemon to run across build steps in a workflow Job (see [#​113](https://togithub.com/gradle/gradle-build-action/issues/113)) ##### Issues resolved https://github.com/gradle/gradle-build-action/milestone/7?closed=1 #### What's Changed - Use GHA Job Summary to summarize Gradle build results by [@​bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/gradle-build-action/pull/282](https://togithub.com/gradle/gradle-build-action/pull/282) - Various improvements to CI workflows by [@​bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/gradle-build-action/pull/294](https://togithub.com/gradle/gradle-build-action/pull/294) - Extract init scripts and state tracking by [@​bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/gradle-build-action/pull/297](https://togithub.com/gradle/gradle-build-action/pull/297) - Add improved Job Summary with build results and caching report by [@​bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/gradle-build-action/pull/298](https://togithub.com/gradle/gradle-build-action/pull/298) - Fix save/restore of configuration-cache by [@​bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/gradle-build-action/pull/302](https://togithub.com/gradle/gradle-build-action/pull/302) - Improve layout and formatting of Job Summary by [@​bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/gradle-build-action/pull/303](https://togithub.com/gradle/gradle-build-action/pull/303) - Default to `cache-read-only` for non-default branches by [@​bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/gradle-build-action/pull/149](https://togithub.com/gradle/gradle-build-action/pull/149) - Improve init scripts and add test coverage by [@​bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/gradle-build-action/pull/304](https://togithub.com/gradle/gradle-build-action/pull/304) - Allow daemons to run across workflow steps by [@​bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/gradle-build-action/pull/305](https://togithub.com/gradle/gradle-build-action/pull/305) - Use java to determine user.home dir by [@​bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/gradle-build-action/pull/306](https://togithub.com/gradle/gradle-build-action/pull/306) **Full Changelog**: https://github.com/gradle/gradle-build-action/compare/v2.1.7...v2.2.0 ### [`v2.1.7`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.1.7) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.1.6...v2.1.7) Fixes [#​293](https://togithub.com/gradle/gradle-build-action/issues/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. - \[FIX] Retain more items in the `wrapper` folder of Gradle User Home, avoiding re-download of wrapper distributions. ### [`v2.1.6`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.1.6) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.1.5...v2.1.6) 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](https://togithub.com/gradle/gradle/issues/3605). This release of `gradle-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 - \[FIX] Save/restore exploded Gradle dist rather than zip - \[FIX] Update to the latest versions of `@actions/core`, `@actions/cache`, `@actions/github`, `@actions/http-client` and `@actions/tool-cache`. **Full changelog**: https://github.com/gradle/gradle-build-action/compare/v2.1.5...v2.1.6 ### [`v2.1.5`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.1.5) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.1.4...v2.1.5) 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 - \[FIX] - Upgrade minimist from 1.2.5 -> 1.2.6 - \[FIX] - Support cache entries > 2Gb via library upgrade to [@​actions/cache](https://togithub.com/actions/cache) from 1.0.10 -> 2.0.0. **Full changelog**: https://github.com/gradle/gradle-build-action/compare/v2.1.4...v2.1.5 ### [`v2.1.4`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.1.4) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.1.3...v2.1.4) ##### What's Changed - Updated dependency versions: [`d700906`](https://togithub.com/gradle/gradle-build-action/commit/d700906a155ae3ddc36d15f41d1ac83e8623287c). - Log stack trace for cache errors that are reported as warnings. **Full Changelog**: https://github.com/gradle/gradle-build-action/compare/v2.1.3...v2.1.4 ### [`v2.1.3`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.1.3) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.1.2...v2.1.3) This patch release fixes an issue that prevented the Gradle User Home from being restored from cache on `macos-latest` runners. [#​155](https://togithub.com/gradle/gradle-build-action/issues/155) #### What's Changed - Fix detection of Gradle User Home on macOS runners by [@​bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/gradle-build-action/pull/156](https://togithub.com/gradle/gradle-build-action/pull/156) **Full Changelog**: https://github.com/gradle/gradle-build-action/compare/v2.1.2...v2.1.3 ### [`v2.1.2`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.1.2) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.1.1...v2.1.2) This patch release fixes a minor bug and updates some NPM dependencies, including one dependency with a reported security advisory. #### What's Changed - Fixed [#​147](https://togithub.com/gradle/gradle-build-action/issues/147): existing `gradle.properties` is no longer overwritten by action initialization - Updated all NPM dependencies to the latest version - This included updating `node-fetch` to a version that isn't impacted by https://github.com/advisories/GHSA-r683-j2x4-v87g. Note that this CVE has been determined not to impact the action. **Full Changelog**: https://github.com/gradle/gradle-build-action/compare/v2.1.1...v2.1.2 ### [`v2.1.1`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.1.1) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.1.0...v2.1.1) This release improves logging and fixes a number of minor issues. - Fix misleading error message when `gradlew` script is not executable [#​76](https://togithub.com/gradle/gradle-build-action/issues/76) - Differentiate between build scan links generated for different steps in the same Job [#​124](https://togithub.com/gradle/gradle-build-action/issues/124) - Avoid overwriting existing Gradle User Home [#​138](https://togithub.com/gradle/gradle-build-action/issues/138) - Capture build scan links even when cache is disabled [#​139](https://togithub.com/gradle/gradle-build-action/issues/139) In addition, 2 experimental configuration parameters have been added: - `gradle-home-cache-strict-match`: Only reuse cache entries generated by previous invocations for the same job - `cache-write-only`: Do not restore cache entries but save on Job completion **Full Changelog**: https://github.com/gradle/gradle-build-action/compare/v2.1.0...v2.1.1 ### [`v2.1.0`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.1.0) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2.0.1...v2.1.0) #### 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. ```yaml jobs: build-my-app: steps: - uses: actions/checkout@v2 - name: Setup Gradle uses: gradle/gradle-build-action@v2 - name: Execute Gradle build run: ./gradlew build ``` 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 subsequent `gradle-build-action`. This is achieved via `init` 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: - Redirect all Gradle log output to a file [#​72](https://togithub.com/gradle/gradle-build-action/issues/72) - Run a script to configure the environment prior to Gradle invocation [#​15](https://togithub.com/gradle/gradle-build-action/issues/15) - Capture Gradle output for use in a subsequent step [#​112](https://togithub.com/gradle/gradle-build-action/issues/112) ##### Usability improvements - Can use regular `run` step to invoke Gradle and still benefit from Gradle User Home caching as well as build-scan integration. ##### Caching improvements - Wrapper distributions and generated API jars are now cached individually, allowing for better reuse and more efficient storage: [#​78](https://togithub.com/gradle/gradle-build-action/issues/78) - Java distributions downloaded by Gradle are cached: [#​33](https://togithub.com/gradle/gradle-build-action/issues/33) #### Changes in detail - Avoid using command-line modification to enhance build execution by [@​bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/gradle-build-action/pull/123](https://togithub.com/gradle/gradle-build-action/pull/123) - Refactor: use a single .json file to describe all cached artifact bundles by [@​bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/gradle-build-action/pull/121](https://togithub.com/gradle/gradle-build-action/pull/121) - Cache wrapper zips and generated jars individually by [@​bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/gradle-build-action/pull/127](https://togithub.com/gradle/gradle-build-action/pull/127) - Restore/save configuration-cache data in first action step by [@​bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/gradle-build-action/pull/128](https://togithub.com/gradle/gradle-build-action/pull/128) - Allow action to be used without Gradle execution by [@​bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/gradle-build-action/pull/130](https://togithub.com/gradle/gradle-build-action/pull/130) - Cache downloaded Java Toolchains by [@​bigdaz](https://togithub.com/bigdaz) in [https://github.com/gradle/gradle-build-action/pull/131](https://togithub.com/gradle/gradle-build-action/pull/131) **Full Changelog**: https://github.com/gradle/gradle-build-action/compare/v2.0.0...v2.1.0 ### [`v2.0.1`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.0.1) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2...v2.0.1) #### 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 - Cache upload failure because file read failed should not cause step to fail [#​120](https://togithub.com/gradle/gradle-build-action/issues/120) - SyntaxError: Unexpected end of JSON input should not cause step to fail [#​119](https://togithub.com/gradle/gradle-build-action/issues/119) **Full Changelog**: https://github.com/gradle/gradle-build-action/compare/v2.0.0...v2.0.1

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.