Skip to content

Upgrade Gradle to 9.9.1 - #30

Merged
lagergren merged 1 commit into
masterfrom
gradle-9.9.1-upgrade
Nov 11, 2026
Merged

lagergren merged 1 commit into
masterfrom
gradle-9.9.1-upgrade

Conversation

@lagergren

Copy link
Copy Markdown
Contributor

Updates the Gradle wrapper from 9.8.2 to 9.9.1, following the same steps as the 9.8.x upgrades and matching xtclang/xvm#766. 9.9.1 is the 9.9.0 feature set plus fixes for three security vulnerabilities in 9.9.0 (version catalog values run as code in generated accessors, and two daemon registry trust issues).

Gradle 9.9.1

  • gradle/wrapper/: distribution URL bumped to gradle-9.9.1-bin.zip. Wrapper regenerated with ./gradlew wrapper --gradle-version 9.9.1 --distribution-type bin, run twice. The jar's SHA-256 (621008af…) matches the published 9.9.1 wrapper checksum. gradlew and gradlew.bat are unchanged, and the wrapper keeps its retry policy.
  • gradle/gradle-daemon-jvm.properties: refreshed with ./gradlew updateDaemonJvm --jvm-version 25. The macOS and Windows JDK 25 builds are newer; the file now matches xvm's.

I went through the 9.8 → 9.9 upgrade guide: the Ant integration and implicit Ant classes on the build script classpath (for example ReplaceTokens filters), Kotlin DSL zipTo/unzipTo, service injection into value source parameters, the temporary Configuration Cache opt-out properties, non-required plugin versions in the version catalog, the legacy lock file format, required input files with absent nested providers, and running Gradle outside a project directory. None of these apply to this build. CI actions are already on the same major versions as xvm.

The Dockerfile builds with ./gradlew, so it names no Gradle version and needs no change.

Verification

  • ./gradlew clean, then ./gradlew build installDist :welcome:runXtc --rerun-tasks --no-build-cache --warning-mode=all: BUILD SUCCESSFUL, 46 tasks. No deprecation warnings. All 56 xunit suites pass with no failures, errors or skips, the same 56 as master's last CI run.
  • A second run reuses the configuration cache.

The build still prints [plugin] WARNING: Project 'gradle-kotlin-dsl-accessors' has unspecified version. once, during :build-logic:generatePrecompiledScriptPluginAccessors. Master's CI already prints it on 9.8.2. The project it names is not one of ours: Gradle creates it to apply xtc-conventions' plugins {} block and generate the accessors, and the XTC plugin's apply-time version check fires on it. The examples projects are versioned (version=0.1.0 in gradle.properties, and chess-game sets its own). The fix belongs in the plugin's checkProjectIsVersioned, so this PR leaves it alone.

The Docker image was not built locally; this PR's CI skips the master-only Docker job.

- gradle/wrapper: distributionUrl bumped to 9.9.1; the wrapper jar is
  regenerated by `./gradlew wrapper --gradle-version 9.9.1 --distribution-type bin`
  (run twice). gradlew and gradlew.bat are unchanged, and the wrapper
  keeps its retry policy.
- gradle/gradle-daemon-jvm.properties: refreshed by
  `./gradlew updateDaemonJvm --jvm-version 25`; the macOS and Windows
  JDK 25 builds are newer. It now matches xtclang/xvm's.

9.9.1 rather than 9.9.0: it is the 9.9.0 feature set plus fixes for
three security vulnerabilities in 9.9.0. The Dockerfile builds with
./gradlew, so it names no Gradle version.

Wrapper jar SHA-256 matches the published 9.9.1 checksum. After clean,
build installDist :welcome:runXtc passes with --rerun-tasks
--no-build-cache --warning-mode=all, with no deprecation warnings; all
56 xunit suites pass, the same 56 as master's CI. A second build reuses
the configuration cache.
@lagergren
lagergren enabled auto-merge (squash) November 10, 2026 21:51
@lagergren
lagergren disabled auto-merge November 10, 2026 21:52
@lagergren
lagergren merged commit e064365 into master Nov 11, 2026
2 checks passed
@lagergren
lagergren deleted the gradle-9.9.1-upgrade branch November 11, 2026 09:44
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