Bump gradle/wrapper-validation-action from 1 to 2

[dependabot]

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

• Security vulnerability: Bump json5 from 1.0.1 to 1.0.2
• Security vulnerability: Bump qs from 6.10.1 to 6.11.0

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

• Retry connections to the server on failure (#39)
• Update dependencies (#38, #37, #36, #34, #31, #30, #29)

v1.0.3

Gradle Wrapper Validation

Update minimist version to 1.2.5

v1.0.2

... (truncated)

Commits

• 699bb18 Build outputs
• 69d55fa Update known wrapper checksums
• e636552 Bump the npm-dependencies group with 1 update
• 85cde3f Add clarification about running in repository root
• 8a2cbc9 Clarify that wrapper-validation should precede setup-gradle
• d355de3 Build outputs
• ac96f18 Hardcoded checksums follow-up
• ca85ed0 Extend integration tests
• c4ee1cd Update known wrapper checksums
• a3555ef Clarify output format (#177)
• Additional commits viewable in compare view

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 <dependency name> 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)

Check List

• New functionality includes testing.
  • All tests pass
• New functionality has been documented.
  • New functionality has javadoc added
• Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
• Commits are signed per the DCO using --signoff
• Commit changes are listed out in CHANGELOG.md file (See: Changelog)
• Public documentation issue/PR created

[github-actions]

Compatibility status:

Checks if related components are compatible with change f2b770d

Incompatible components

Skipped components

Compatible components

Compatible components: [https://github.com/opensearch-project/custom-codecs.git, https://github.com/opensearch-project/flow-framework.git, https://github.com/opensearch-project/neural-search.git, https://github.com/opensearch-project/opensearch-oci-object-storage.git, https://github.com/opensearch-project/cross-cluster-replication.git, https://github.com/opensearch-project/job-scheduler.git, https://github.com/opensearch-project/security-analytics.git, https://github.com/opensearch-project/observability.git, https://github.com/opensearch-project/geospatial.git, https://github.com/opensearch-project/k-nn.git, https://github.com/opensearch-project/notifications.git, https://github.com/opensearch-project/asynchronous-search.git, https://github.com/opensearch-project/reporting.git, https://github.com/opensearch-project/ml-commons.git, https://github.com/opensearch-project/sql.git, https://github.com/opensearch-project/common-utils.git, https://github.com/opensearch-project/index-management.git, https://github.com/opensearch-project/anomaly-detection.git, https://github.com/opensearch-project/alerting.git, https://github.com/opensearch-project/performance-analyzer-rca.git, https://github.com/opensearch-project/security.git, https://github.com/opensearch-project/performance-analyzer.git]

[github-actions]

❌ Gradle check result for cbf5484: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for f2b770d: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[peternied]

Flaky Tests:

• [BUG] org.opensearch.search.SearchWeightedRoutingIT.testShardRoutingWithNetworkDisruption_FailOpenEnabled is flaky #10673
• [BUG] org.opensearch.remotestore.RemoteIndexPrimaryRelocationIT.testPrimaryRelocationWhileIndexing flaky failure #9191
• [BUG] the org.opensearch.snapshots.DeleteSnapshotIT tests are flaky #9208

[github-actions]

❕ Gradle check result for f2b770d: UNSTABLE

• TEST FAILURES:

      1 org.opensearch.search.SearchWeightedRoutingIT.testMultiGetWithNetworkDisruption_FailOpenEnabled
      1 org.opensearch.remotestore.RemoteIndexPrimaryRelocationIT.testPrimaryRelocationWhileIndexing

Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (b19e427) 71.34% compared to head (f2b770d) 71.38%.
Report is 3 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff              @@
##               main   #12367      +/-   ##
============================================
+ Coverage     71.34%   71.38%   +0.04%     
- Complexity    59771    59775       +4     
============================================
  Files          4960     4960              
  Lines        281164   281166       +2     
  Branches      40862    40861       -1     
============================================
+ Hits         200590   200722     +132     
+ Misses        63872    63778      -94     
+ Partials      16702    16666      -36     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[opensearch-trigger-bot]

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/OpenSearch/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch/backport-2.x
# Create a new branch
git switch --create backport/backport-12367-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 75d64e2bf3da15636c2b22753f6f99560aa77b82
# Push it to GitHub
git push --set-upstream origin backport/backport-12367-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-12367-to-2.x.