# Gradle Release Notes

We are excited to announce Gradle 9.5.0-20260325015243+0000 (released 2026-03-25).

This release features 1, 2, ... n, and more.

We would like to thank the following community members for their contributions to this release of Gradle: /dev/mataha, Adam, Attila Kelemen, Benedikt Ritter, Björn Kautler, Caro Silva Rode, CHANHAN, Eng Zer Jun, Madalin Valceleanu, Markus Gaisbauer, Philip Wedemann, ploober, Roberto Perez Alcolea, Rohit Anand, Suvrat Acharya, Ujwal Suresh Vanjare, Victor Merkulov.

Be sure to check out the public roadmap for insight into what's planned for future releases.

## Table Of Contents

## Upgrade instructions

Switch your build to use Gradle 9.5.0-20260325015243+0000 by updating the wrapper in your project:

    ./gradlew wrapper --gradle-version=9.5.0-20260325015243+0000 && ./gradlew wrapper

See the Gradle 9.x upgrade guide to learn about deprecations, breaking changes, and other considerations when upgrading to Gradle 9.5.0-20260325015243+0000.

For Java, Groovy, Kotlin, and Android compatibility, see the full compatibility notes.

## New features and usability improvements

### Core plugin and plugin authoring enhancements

Gradle provides a comprehensive plugin system, including built-in Core Plugins for standard tasks and powerful APIs for creating custom plugins.

### Automatic retries for Wrapper downloads

The Gradle Wrapper now supports automatic retries when downloading the Gradle distribution. This helps reduce build failures caused by unstable network connections or temporary server issues. By default, no retries are attempted.

To enable retries, add the following properties to `gradle-wrapper.properties`:

    retries=3 # Sets the maximum number of retry attempts
    retryTimeoutMs=5000 # Sets the delay between retries

#### Type-safe accessors for precompiled Kotlin Settings plugins

Gradle now generates type-safe Kotlin accessors for precompiled convention Settings plugins (`*.settings.gradle.kts`).

Previously, when writing a convention plugin for `settings.gradle.kts`, you often had to use string-based APIs to configure extensions or plugins. Now, as long as the `kotlin-dsl` plugin is applied, Gradle generates accessors that provide IDE autocompletion and compile-time checking for your settings scripts, matching the experience already available for Project-level convention plugins.

To enable these accessors, ensure your convention plugin build includes the `kotlin-dsl` plugin:

    // build-logic/build.gradle.kts
    plugins {
        `kotlin-dsl`
    }

### Build authoring improvements

Gradle provides rich APIs for build engineers and plugin authors, enabling the creation of custom, reusable build logic and better maintainability.

#### Domain Object Collections can be made immutable

Plugin and build authors can now lock domain object collections to prevent further modifications using the new `disallowChanges()` method:

- Once `disallowChanges()` is called, elements can no longer be added to or removed from the collection.
- Invoking this method does not force the realization of lazy items previously added to the collection.
- This lock applies only to the collection itself. Individual objects within the collection can still be modified.

    val myCollection = objects.domainObjectContainer(MyType::class)
    val main = MyType("main")

    myCollection.add(main)
    myCollection.add(MyType("test"))

    myCollection.disallowChanges()    // the collection is now immutable
    main.setFoo("bar")                // individual elements can still be modified

    myCollection.add(MyType("other")) // this will fail
    myCollection.remove(main)         // this will fail

#### GitHub permalinks in Gradle Wrapper and application start scripts

Gradle Wrapper scripts and application start scripts now include links to the GitHub source templates they were generated from.

Previously, these links always pointed to the latest template versions rather than the version used to generate the script. In this release, scripts link to the exact template version they were generated from.

#### Explicit bind address for client-daemon and cross-daemon communication

Gradle now supports the `GRADLE_DAEMON_BIND_ADDRESS` environment variable to explicitly specify the network address used for client-daemon and cross-daemon communication.

Previously, Gradle always attempted to auto-detect the local bind address, which could fail in environments with specific network configurations (multiple network interfaces, multiple TCP/IP stacks, etc.).

Setting `GRADLE_DAEMON_BIND_ADDRESS` to an IP address or hostname will skip auto-detection and use the provided address directly:

    GRADLE_DAEMON_BIND_ADDRESS=192.168.1.10 ./gradlew build

### Diagnostics and reporting improvements

Gradle provides built-in reporting tasks to help you understand and troubleshoot your build.

#### Task provenance in reports and failure messages

Gradle now displays provenance information for tasks — the plugin or build script that registered each task. This makes it easier to understand where tasks come from and diagnose failures in complex builds with many plugins.

Task reports: The `tasks` report now supports a `--provenance` option that shows where each task was registered:

    > ./gradlew tasks --provenance

    Build tasks
    -----------
    assemble - Assembles the outputs of this project. (registered by plugin 'org.gradle.language.base.plugins.LifecycleBasePlugin')
    build - Assembles and tests this project. (registered by plugin 'org.gradle.language.base.plugins.LifecycleBasePlugin')

Help task: When using `help --task`, the output now includes provenance alongside each task path.

Failure messages: When a task fails, the error message now indicates where the failing task was registered, helping you quickly identify the responsible plugin or script:

    Execution failed for task ':app:compileJava' (registered by plugin 'org.gradle.api.plugins.JavaPlugin').

Provenance is omitted from failure messages for verification failures (e.g., test failures), since those are expected outcomes rather than configuration issues.

### Tooling and IDE integration

Gradle provides Tooling APIs that facilitate deep integration with modern IDEs and CI/CD pipelines.

#### Tooling integration improvements

Tooling API clients can now directly access Gradle help and version information the same way as the Gradle CLI. This allows IDEs and other tools to provide a more consistent user experience when interacting with Gradle.

For example, In IntelliJ IDEA users will be able to run `--help` and `--version` via the `Execute Gradle task` toolbar action.

## Promoted features

Promoted features are features that were incubating in previous versions of Gradle but are now supported and subject to backward compatibility. See the User Manual section on the "Feature Lifecycle" for more information.

The following are the features that have been promoted in this Gradle release.

## Fixed issues

## Known issues

Known issues are problems that were discovered post-release that are directly related to changes made in this release.

## External contributions

We love getting contributions from the Gradle community. For information on contributing, please see gradle.org/contribute.

## Reporting problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure if you're encountering a bug, please use the forum.

We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.