aepfli / gradle-gitlab-repositories

Handling Maven GitLab dependencies made easy. Define multiple tokens and selectively apply them to repositories, remove the need for repeating Credential handling blocks for different environments.
Eclipse Public License 2.0
13 stars 1 forks source link

Update eskatos/gradle-command-action action to v2.3.1 #48

Closed renovate[bot] closed 2 years ago

renovate[bot] commented 2 years ago

Mend Renovate

This PR contains the following updates:

Package Type Update Change
eskatos/gradle-command-action action minor v2.1.5 -> v2.3.1

⚠ Dependency Lookup Warnings ⚠

Warnings were logged while processing this repo. Please check the logs for more information.


Release Notes

eskatos/gradle-command-action ### [`v2.3.1`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.3.1) [Compare Source](https://togithub.com/eskatos/gradle-command-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. ### [`v2.3.0`](https://togithub.com/gradle/gradle-build-action/releases/tag/v2.3.0) [Compare Source](https://togithub.com/eskatos/gradle-command-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/eskatos/gradle-command-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/eskatos/gradle-command-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/eskatos/gradle-command-action/compare/v2.2.3...v2.2.4) ##### What's fixed The fix for [#​383](https://togithub.com/eskatos/gradle-command-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/eskatos/gradle-command-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/eskatos/gradle-command-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/eskatos/gradle-command-action/issues/383)) - Fix reporting of caching errors that was broken in `v2.2.2` ([#​407](https://togithub.com/eskatos/gradle-command-action/issues/407)) - Abort cache download operations after 10 minutes (configurable). Previously cache download operations could hang the build. ([#​369](https://togithub.com/eskatos/gradle-command-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/eskatos/gradle-command-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/eskatos/gradle-command-action/issues/341)) - Only write build-results file when GitHub Actions env vars are available ([#​350](https://togithub.com/eskatos/gradle-command-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/eskatos/gradle-command-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/eskatos/gradle-command-action/issues/319) - Fix warning when attempting to delete non-existent file: [#​308](https://togithub.com/eskatos/gradle-command-action/issues/308) - Fix `Entry not saved: reason unknown` message in Job Summary cache details: [#​309](https://togithub.com/eskatos/gradle-command-action/issues/309) - Report failure to publish build scan in Job Summary: [#​326](https://togithub.com/eskatos/gradle-command-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/eskatos/gradle-command-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/eskatos/gradle-command-action/commit/0a36ca9fb8a7acc820f34da9116f389a13dc67e2)) - Allow the Gradle Daemon to run across build steps in a workflow Job (see [#​113](https://togithub.com/eskatos/gradle-command-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/eskatos/gradle-command-action/compare/v2.1.6...v2.1.7) Fixes [#​293](https://togithub.com/eskatos/gradle-command-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/eskatos/gradle-command-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

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.

cla-bot[bot] commented 2 years ago

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have the users @renovate[bot] on file. In order for us to review and merge your code, please contact the project maintainers to get yourself added.

cla-bot[bot] commented 2 years ago

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have the users @renovate[bot] on file. In order for us to review and merge your code, please contact the project maintainers to get yourself added.

aepfli commented 2 years ago

@cla-bot check

cla-bot[bot] commented 2 years ago

The cla-bot has been summoned, and re-checked this pull request!