Skip to content

Update dependency java-jdk to v25 - #975

Merged
DreierF merged 3 commits into
masterfrom
renovate/java-jdk-25.x
Sep 17, 2026
Merged

DreierF merged 3 commits into
masterfrom
renovate/java-jdk-25.x

Conversation

@renovate

@renovate renovate Bot commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
java-jdk uses-with major 21 → 25

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot requested a review from DreierF September 16, 2026 20:21
A build that fails while configuring writes nothing but the daemon notice to stdout and reports what went
wrong on stderr. runGradle handed that result back to the caller, so the test failed on whatever it asserted
about the coverage the build never produced, and the actual cause never reached the test report. That is
what makes the current Windows failures of gradle-multi-module unreadable.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
gradle-daemon-jvm.properties made the fixture's own Gradle daemon require Java 21, which is stricter than
the Java 21 toolchain the projects compile against: the daemon's JVM is picked by the launcher before the
settings script runs, so the toolchain repository that foojay registers there does not exist yet and the
JDK cannot be provisioned either. As long as the runners ran Gradle on Java 21 the launcher's own JVM
satisfied it. On Java 25 it no longer does, and only Linux keeps its JDKs somewhere the launcher detects
(/usr/lib/jvm); on Windows they live in the tool cache, so every nested build there failed with

    Unable to download toolchain matching the requirements ({languageVersion=21, ...}) from 'null', due to:
    No defined toolchain download url for WINDOWS on x86_64 architecture.

The file is the only one of its kind in the repository and arrived as a stray in an unrelated commit; no
test says anything about the daemon's JVM. The projects keep their Java 21 toolchain, which resolves
normally once the build is running.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@renovate

renovate Bot commented Sep 17, 2026

Copy link
Copy Markdown
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@DreierF
DreierF enabled auto-merge September 17, 2026 07:17
@DreierF
DreierF merged commit 139c091 into master Sep 17, 2026
6 checks passed
@renovate
renovate Bot deleted the renovate/java-jdk-25.x branch September 17, 2026 07:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant