Bumps gradle/wrapper-validation-action from 1 to 2.

Release notes

Sourced from gradle/wrapper-validation-action's releases.

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)

v2.0.0-rc.1

This is a release candidate for v2.0.0. It is also available under the v2 version label.

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.

  • [NEW] Update Node.js runtime to version 20 (#170)

v1.1.0

The action now adds the path of the failed wrapper Jar as a failed-wrapper Step output parameter. This makes the value available for reporting in later Steps/Jobs.

v1.0.6

Gradle Wrapper Validation

v1.0.5

Gradle Wrapper Validation

  • Update dependencies for Node 16 (#53)
  • Update dependencies with security vulnerabilities (#67)
  • Update various other dependencies (#45, #47, #48, #54)

v1.0.4

Gradle Wrapper Validation

v1.0.3

Gradle Wrapper Validation

Update minimist version to 1.2.5

v1.0.2

... (truncated)

Commits
  • 27152f6 Update to Node 20 (#170)
  • d8758a9 Build output
  • e916071 Update NPM dependencies
  • d9359e4 Add asdf config file
  • 77d43de Update upload-artifact version
  • 2f8436d Use setup-node@v4 instead of pinning to a revision
  • bfa0fe4 Consistently use npm cache for workflows
  • 8be8473 Update workflows and action to NodeJS 20
  • c8fad9e Bump @​babel/traverse from 7.14.7 to 7.23.2
  • 342dbeb Update README to use actions/checkout@v4
  • See full diff in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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)

Comment From: dependabot[bot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.