Skip to content

Update to use JDK 21 for build#660

Merged
gareth-ellis merged 2 commits intomasterfrom
use-jdk-21-build
Sep 12, 2024
Merged

Update to use JDK 21 for build#660
gareth-ellis merged 2 commits intomasterfrom
use-jdk-21-build

Conversation

@gareth-ellis
Copy link
Member

This updates the build JDK to 21, since Elasticsearch@main now requires 21 to build. I bumped the github action versions too at the same time

@gareth-ellis gareth-ellis requested a review from a team September 12, 2024 12:24
Copy link
Contributor

@favilo favilo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would hope that an upgrade would just work with default options

@gareth-ellis gareth-ellis merged commit 74d31cd into master Sep 12, 2024
gareth-ellis added a commit that referenced this pull request Sep 16, 2024
* Update to use JDK 21 for build
gareth-ellis added a commit that referenced this pull request Sep 16, 2024
* Update to use JDK 21 for build
gbanasiak pushed a commit to gbanasiak/rally-tracks that referenced this pull request Sep 19, 2024
* Update to use JDK 21 for build
@gbanasiak gbanasiak mentioned this pull request Sep 19, 2024
gbanasiak added a commit that referenced this pull request Sep 19, 2024
@gareth-ellis gareth-ellis deleted the use-jdk-21-build branch August 18, 2025 15:53
@esbenchmachine esbenchmachine added the backport pending Awaiting backport to stable release branch label Dec 19, 2025
@esbenchmachine
Copy link
Collaborator

@gareth-ellis
A backport is pending for this PR. Please add all required vX.Y version labels.

  • If it is intended for the current Elasticsearch release version, apply the corresponding version label.
  • If it also supports past released versions, add those labels too.
  • If it only targets a future version, wait until that version label exists and then add it.
    (Each rally-tracks version label is created during the feature freeze of a new Elasticsearch branch).

Backporting entails:

  1. Ensure the correct version labels exist in this PR.
  2. Ensure backport PRs have backport label and are passing tests.
  3. Merge backport PRs (you can approve yourself and enable auto-merge).
  4. Remove backport pending label from this PR once all backport PRs are merged.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport pending Awaiting backport to stable release branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

Comments