Bump actions/setup-java from 1 to 4

[dependabot]

Bumps actions/setup-java from 1 to 4.

Release notes

Sourced from actions/setup-java's releases.

v4.0.0

What's Changed

In the scope of this release, the version of the Node.js runtime was updated to 20. The majority of dependencies were updated to the latest versions. From now on, the code for the setup-java will run on Node.js 20 instead of Node.js 16.

Breaking changes

• Update Node.js runtime to version 20 by @​aparnajyothi-y in actions/setup-java#558

Non-breaking changes

• Adding support for microsoft openjdk 21.0.0 by @​ralfstuckert in actions/setup-java#546
• Update @​actions/cache dependency and documentation by @​IvanZosimov in actions/setup-java#549
• Implementation of the cache-dependency-path option to control caching dependency by @​itchyny in actions/setup-java#499

New Contributors

• @​ralfstuckert made their first contribution in actions/setup-java#546
• @​itchyny made their first contribution in actions/setup-java#499

Full Changelog: actions/setup-java@v3...v4.0.0

v3.13.0

What's changed

In the scope of this release, support for Dragonwell JDK was added by @​Accelerator1996 in actions/setup-java#532

steps:
 - name: Checkout
   uses: actions/checkout@v3
 - name: Setup-java
   uses: actions/setup-java@v3
   with:
     distribution: 'dragonwell'
     java-version: '17'

Several inaccuracies were also fixed:

• Fix XML namespaces wrongly using https by @​gnodet in actions/setup-java#503
• Fix typo and remove unintentional(?) word by @​CyberFlameGO in actions/setup-java#518
• Fix usage link within the README.md file by @​dassiorleando in actions/setup-java#525

New Contributors

• @​CyberFlameGO made their first contribution in actions/setup-java#518
• @​dassiorleando made their first contribution in actions/setup-java#525
• @​gnodet made their first contribution in actions/setup-java#503
• @​Accelerator1996 made their first contribution in actions/setup-java#532

Full Changelog: actions/setup-java@v3...v3.13.0

v3.12.0

... (truncated)

Commits

• 99b8673 Patch for java version file (#610)
• 5896cec Added .tool-versions file support (#606)
• 80ae3c2 Update httpclient version and other dependencies (#607)
• 9704b39 Added Windows Arm64 Support for Windows Arm64 Runners (#595)
• 7a445ee Fix typo in configuration example (#572)
• 3232623 Oracle JDK 21 support (#538)
• c0660d8 docs: add note about maven-gpg-plugin version (#570)
• 2f7af1b make it clear that Java 21 is supported (#566)
• 16ef37f HTTP errors when the token is undefined (#556)
• a237454 feat: bump actions/checkout and actions/setup-java to v4 (#533)
• 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)

[peternied]

Since this GitHub action is triggered on comments which require the actions is on the main branch, it doesn't seem useful to backport onto the 2.x branch.

@reta what do you think, should we limit the backport when they don't have an impact, or should we be less discriminating to make it easier to identify inconsistencies?

[reta]

@reta what do you think, should we limit the backport when they don't have an impact, or should we be less discriminating to make it easier to identify inconsistencies?

Good question @peternied , I think we definitely don't need to backport everything but this one would probably make sense to keep consistent across branches.

[kotwanikunal]

@dependabot recreate

[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-15104-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 7cbff4f9fd8ae53b1672aa8e2582e23bb2c16def
# Push it to GitHub
git push --set-upstream origin backport/backport-15104-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-15104-to-2.x.

[peternied]

Looks like we never backported .github/workflows/benchmark-pull-request.yml, I'm going to hold off on pulling in these changes.