Skip to content

Update .tool-versions: node 24.18.0, gradle 9.7.1, java 17 - #1068

Merged
bigdaz merged 2 commits into
mainfrom
dd/bump-tool-versions
Sep 7, 2026
Merged

bigdaz merged 2 commits into
mainfrom
dd/bump-tool-versions

Conversation

@bigdaz

@bigdaz bigdaz commented Sep 7, 2026

Copy link
Copy Markdown
Member

The pins in .tool-versions had drifted well behind what CI and the Gradle wrappers use. One of
them was not just stale but broken.

node 24.3.0 β†’ 24.18.0

CI runs node-version: 24, which resolves to a much newer 24.x. That gap is not harmless: it
recently masked a real CI failure outright, because jest 30.5.0's breakage of nock interception
reproduces on 24.18.0 but not on 24.3.0. A local run that passes is worth something again.

Verified with a clean ./build install and repeated ./build test runs on both versions. Both show
the same stable core of two failures β€” the network-dependent wrapper-validation checksum tests β€”
plus an occasional third flake in the same area that varies between runs and between node versions.
Nothing attributable to the bump.

java liberica-11 β†’ liberica-17

This pin was broken. The init-scripts wrapper is on Gradle 9.7.1, which refuses to run a build on
JVM 11:

Gradle requires JVM 17 or later to run.
Your build is currently configured to use JVM 11.

So ./build init-scripts could not have worked with the pinned toolchain. ./gradlew --version
does start under JVM 11 and reports successfully, which is likely how the pin survived unnoticed β€”
only an actual build fails.

17 matches what ci-init-script-check.yml provisions, so local runs mirror CI. Verified with a
clean ./gradlew check in sources/test/init-scripts: BUILD SUCCESSFUL in 3m57s.

Java 21 was also tried and passes (3m53s), so moving further later is unblocked. 17 is chosen only
to track CI.

gradle 8.14.2 β†’ 9.7.1

Follows the wrappers, which the workflow samples and init-scripts tests are now on. This matches how
the file has been maintained before (e.g. "Use Gradle 8.14 everywhere"). Nothing in ./build
invokes the asdf gradle β€” every path goes through ./gradlew β€” so this only keeps ad-hoc CLI use
consistent.

Notes

ci-check-and-unit-test.yml still provisions gradle-version: '8.14.2' for its unit-test job.
That may be equally stale, but it is a CI behaviour change rather than local tooling, so it is left
alone here.

One flaky run was seen while verifying: two TestDevelocityInjection cases against Gradle 6.0.1
failed once, then passed on re-run and on repeat clean builds. Unrelated to these version changes.

πŸ€– Generated with Claude Code

bigdaz and others added 2 commits September 7, 2026 17:10
The asdf pin was 24.3.0 while CI runs `node-version: 24`, which resolves
to a much newer 24.x. That gap is not harmless: it recently masked a real
CI failure entirely, because jest 30.5.0's breakage of nock interception
reproduces on 24.18.0 but not on 24.3.0. Pinning closer to CI means local
runs are worth something again.

Verified with a clean `./build install` and repeated `./build test` runs
on both versions. Both show the same stable core of two failures, the
network-dependent wrapper-validation checksum tests, plus an occasional
third flake in the same area that varies between runs and between node
versions. No behaviour attributable to the bump.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The java pin was not merely stale, it was broken. The init-scripts
wrapper is on Gradle 9.7.1, which refuses to run a build on JVM 11:

  Gradle requires JVM 17 or later to run.
  Your build is currently configured to use JVM 11.

So `./build init-scripts` could not have worked with the pinned
toolchain. Note `./gradlew --version` does start under JVM 11, which is
probably how the pin survived this long - only an actual build fails.

Java 17 matches what ci-init-script-check.yml provisions, so local runs
now mirror CI. Verified with a clean `./gradlew check` in
sources/test/init-scripts: BUILD SUCCESSFUL in 3m57s. Java 21 was also
tried and passes (3m53s), so a later move is unblocked; 17 is chosen
only to track CI.

Gradle follows the wrappers, which the samples and init-scripts tests
moved to 9.7.1. That matches how this file has been maintained before,
e.g. "Use Gradle 8.14 everywhere". Nothing in `./build` invokes the asdf
gradle - every path goes through ./gradlew - so this keeps ad-hoc CLI use
consistent rather than changing what the build does.

One flaky run was seen along the way: two TestDevelocityInjection cases
against Gradle 6.0.1 failed once and passed on re-run and on repeat clean
builds. Unrelated to the version change.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@bigdaz
bigdaz merged commit 7927085 into main Sep 7, 2026
139 checks passed
@bigdaz
bigdaz deleted the dd/bump-tool-versions branch September 7, 2026 23:59
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