github-actions[bot]
commented
10 months ago Qodana Community for JVM
It seems all right 👌
No new problems were found according to the checks applied
💡 Qodana analysis was run in the pull request mode: only the changed files were checked
This PR contains the following updates:
v3->v4v3->v4v2->v3v1.1.0->v2.1.1v3->v4Release Notes
actions/cache (actions/cache)
### [`v4`](https://togithub.com/actions/cache/compare/v3...v4) [Compare Source](https://togithub.com/actions/cache/compare/v3...v4)codecov/codecov-action (codecov/codecov-action)
### [`v4`](https://togithub.com/codecov/codecov-action/compare/v3...v4) [Compare Source](https://togithub.com/codecov/codecov-action/compare/v3...v4)gradle/gradle-build-action (gradle/gradle-build-action)
### [`v3`](https://togithub.com/gradle/gradle-build-action/compare/v2...v3) [Compare Source](https://togithub.com/gradle/gradle-build-action/compare/v2...v3)gradle/wrapper-validation-action (gradle/wrapper-validation-action)
### [`v2.1.1`](https://togithub.com/gradle/wrapper-validation-action/releases/tag/v2.1.1) [Compare Source](https://togithub.com/gradle/wrapper-validation-action/compare/v2.1.0...v2.1.1) ##### Changelog - \[FIX] Add hardcoded checksum for Gradle 7.6.4 **Full Changelog**: https://github.com/gradle/wrapper-validation-action/compare/v2...v2.1.1 ### [`v2.1.0`](https://togithub.com/gradle/wrapper-validation-action/releases/tag/v2.1.0) [Compare Source](https://togithub.com/gradle/wrapper-validation-action/compare/v2.0.1...v2.1.0) This release should vastly reduce the number of network requests made by the `wrapper-validation-action`, by hardcoding the checksums of all known Gradle wrapper jars at time of release. With this improvement, a number of long-standing issues should be addressed ([#164](https://togithub.com/gradle/wrapper-validation-action/issues/164), [#162](https://togithub.com/gradle/wrapper-validation-action/issues/162), [#57](https://togithub.com/gradle/wrapper-validation-action/issues/57)). The action should now only make network requests to validate the checksums of an unknown `gradle-wrapper.jar`. This can happen if: - The Gradle version was published after this action was released - The `gradle-wrapper.jar` is truly invalid #### Changelog - \[NEW] Hardcode list of known checksums to avoid network requests in most cases ([#161](https://togithub.com/gradle/wrapper-validation-action/issues/161)) Huge thanks to [@Marcono1234](https://togithub.com/Marcono1234) for contributing this long-awaited improvement. ### [`v2.0.1`](https://togithub.com/gradle/wrapper-validation-action/releases/tag/v2.0.1) [Compare Source](https://togithub.com/gradle/wrapper-validation-action/compare/v2.0.0...v2.0.1) This patch release fixes error reporting when failing to retrieve the checksums from services.gradle.org - \[FIX] After migration from v1 to v2 silently fails ([#174](https://togithub.com/gradle/wrapper-validation-action/issues/174)) ### [`v2.0.0`](https://togithub.com/gradle/wrapper-validation-action/releases/tag/v2.0.0) [Compare Source](https://togithub.com/gradle/wrapper-validation-action/compare/v1.1.0...v2.0.0) #### What's Changed The version of the Node.js runtime was updated to 20, and the majority of dependencies were updated to the latest versions. From now on, the `wrapper-validation-action` will require a Node.js 20 runtime environment. There are no functional changes in this release. This release is tagged with the `v2` version label. - \[NEW] Update Node.js runtime to version 20 ([#170](https://togithub.com/gradle/wrapper-validation-action/issues/170))jtalk/url-health-check-action (jtalk/url-health-check-action)
### [`v4`](https://togithub.com/Jtalk/url-health-check-action/releases/tag/v4): Using Node v20 [Compare Source](https://togithub.com/jtalk/url-health-check-action/compare/v3...v4) Upgrading to Node.js v20 as Github is deprecating v16 in its runners.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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.