Serguey Asael Shinder: Gradle 9.9.0 compiles Kotlin DSL scripts incrementally and filters ArchUnit rules with --tests
Gradle 9.9.0 was released on 6 November. The release notes lead with four changes that touch most JVM builds.
Kotlin DSL scripts are now compiled through the Kotlin Build Tools API, which brings incremental compilation to build scripts. When a script must be recompiled, for instance after a signature change in buildSrc or an included build, only the affected parts are rebuilt. On one large multi-project build in Gradle's performance tests that made recompiling scripts 65% faster. Builds that rarely recompile scripts see no difference.
Test filters now apply to JUnit Platform tests that are not declared as methods, such as ArchUnit rules declared on fields with @ArchTest or Spek scopes. Until now Gradle ran those tests under any --tests filter unless their whole class was excluded, so filtering for one unrelated test still ran every ArchUnit rule. They are now matched by enclosing class and reported name, the way methods are. The Test Retry plugin benefits too: it used to rerun every non-method test whenever any test was retried, and now reruns only the failed ones. Tests that an engine registers only during execution, as Kotest does, can still be selected only by their spec class.

The wrapper task now keeps values from an existing gradle-wrapper.properties when it regenerates the wrapper: distribution type, network timeout, retries and backoff, URL validation, and the distribution and archive paths. It used to reset them to defaults. The distributionUrl is still regenerated for the new version, so a custom host is not preserved.
The incubating Problems API gains a predefined hierarchy of eleven root groups, such as Compilation > Java. The notes warn that legacy problem groups are gone and Gradle's own problem IDs have changed, so Tooling API clients and anything that matches problems by ID need updating. ProviderFactory also gets incubating absent(), present(value) and presentIfNotNull(value) methods, and the user manual is now available as Markdown.
The test-filter change is the one most likely to alter a CI run: a filtered job that used to execute every ArchUnit rule will now run only what it names, which is correct but may hide a rule someone relied on catching.