Skip to content

Conversation

@wendigo
Copy link
Contributor

@wendigo wendigo commented Oct 27, 2025

Description

Additional context and related issues

Release notes

( ) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
(x) Release notes are required, with the following suggested text:

## General
* Update JDK to 25.0.1 ({issue}`issuenumber`)

Summary by Sourcery

Build:

  • Update core/.temurin-release to use jdk-25.0.1+8

@cla-bot cla-bot bot added the cla-signed label Oct 27, 2025
@sourcery-ai
Copy link

sourcery-ai bot commented Oct 27, 2025

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR bumps the project’s Temurin JDK reference from 25.0.1+7 to 25.0.1+8 by updating the core/.temurin-release file, ensuring all subsequent build and CI steps pull in the new JDK patch.

File-Level Changes

Change Details Files
Bump Temurin JDK version
  • Updated the version identifier to jdk-25.0.1+8
  • Replaced the previous release string
  • Retained checksum and metadata format
core/.temurin-release

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

Hey there - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@wendigo wendigo merged commit 97f1088 into master Oct 30, 2025
828 of 843 checks passed
@wendigo wendigo deleted the serafin/jdk-25.0.1 branch October 30, 2025 20:04
@github-actions github-actions bot added this to the 479 milestone Oct 30, 2025
@findepi
Copy link
Member

findepi commented Nov 3, 2025

## General
* Update JDK to 25.0.1 ({issue}`issuenumber`)

What's the end user impact?
Does this PR change JDK version in docker image (previously reported in "Docker image" section https://trino.io/docs/current/release/release-478.html#docker-image), or something else?

BTW if this impacts docker only, should this file live under core/docker folder?

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

Development

Successfully merging this pull request may close these issues.

4 participants