build(deps): bump gradle/actions from 3.5.0 to 4.1.0

dependabot[bot] commented 2 months ago

Bumps gradle/actions from 3.5.0 to 4.1.0.

Release notes

Sourced from gradle/actions's releases.

v4.1.0

This release brings some minor improvements:

The latest release of Gradle is no longer required to perform cache-cleanup. If Gradle is found to on the PATH and the version meets minimum version requirements, then the version on PATH is used for cache-cleanup and Gradle is not downloaded.

Fixes a bug where setting the develocity-token-expiry parameter had no effect (#381)

Numerous NPM dependency updates

Full Changelog: https://github.com/gradle/actions/compare/v4.0.1...v4.1.0

v4.0.1

This patch release updates a number of dependencies, and fixes a bug that caused Gradle version '8.1' to be confused with '8.10'.

What's Changed

Dependency-updates by @bigdaz in gradle/actions#326, gradle/actions#356

NPM dependency updates by @dependabot in gradle/actions#330, gradle/actions#349

Include Gradle 8.10 in known wrapper checksums in gradle/actions#341

Differentiate Gradle 8.1 from 8.10 when checking version by @bigdaz in gradle/actions#358

Full Changelog: https://github.com/gradle/actions/compare/v4.0.0...v4.0.1

v4.0.0

Final release of v4.0.0 of the setup-gradle, dependency-submission and wrapper-validation actions provided under gradle/actions. This release is available under the v4 tag.

Major changes from the v3 release

The arguments parameter has been removed

Using the action to execute Gradle via the arguments parameter was deprecated in v3 and this parameter has been removed. See here for more details.

Cache cleanup enabled by default

After a number of fixes and improvements, this release enables cache-cleanup by default for all Jobs using the setup-gradle and dependency-submission actions.

Improvements and bugfixes related cache cleanup:

By default, cache cleanup is not run if any Gradle build fails (#71)

Cache cleanup is not run after configuration-cache reuse (#19)

This feature should help to minimize the size of entries written to the GitHub Actions cache, speeding up builds and reducing cache usage.

Wrapper validation enabled by default

In v3, the setup-gradle action was enhanced to support Gradle wrapper validation, removing the need to use a separate workflow file with the gradle/actions/wrapper-validation action.

With this release, wrapper validation has been significantly improved, and is now enabled by default (#12):

The allow-snapshot-wrappers makes it possible to validate snapshot wrapper jars using setup-gradle.

Checksums for nightly and snapshot Gradle versions are now validated (#281).

Valid wrapper checksums are cached in Gradle User Home, reducing the need to retrieve checksum values remotely (#172).

Reduce network calls in wrapper-validation for new Gradle versions: By only fetching wrapper checksums for Gradle versions that were not known when this action was released, this release reduces the likelihood that a network failure could cause failure in wrapper validation (#171)

... (truncated)

Commits

d156388 Bump path-to-regexp from 6.2.1 to 6.3.0 in /sources
2e93f41 Bump the npm-dependencies group across 1 directory with 2 updates
ee8dc90 [bot] Update dist directory
5fe9264 Bump references to Develocity Gradle plugin from 3.18 to 3.18.1
29d4d80 Bump the npm-dependencies group across 1 directory with 3 updates
478782d Bump peter-evans/create-pull-request in the github-actions group
e6215ed [bot] Update dist directory
765a734 Fix passing expiresInHours query parameter
a122cf5 Document develocity-token-expiry parameter
5baa1de [bot] Update dist directory
Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

openshift-ci[bot] commented 2 months ago

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Once this PR has been reviewed and has the lgtm label, please assign adietish for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files: - **[OWNERS](https://github.com/redhat-developer/intellij-openshift-connector/blob/main/OWNERS)** Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

openshift-ci[bot] commented 2 months ago

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a redhat-developer member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.