This is a patch release. - **Fixed**: Restored compatibility with **Java 11**. The `2025.1.0` release accidentally required Java 17 due to a build toolchain upgrade. This caused dependency resolution failures for projects using older JDKs. This version corrects the Java target back to 11 (#484, #485). **Full Changelog from 2025.1.0**: 2025.1.0...2025.1.1

Generated from the API spec of [Develocity API 2025.1][1]. - [Develocity API changelog][2] - [Library API diff (see `library.api`)][3] [1]: https://docs.gradle.com/enterprise/api-manual/#reference_documentation [2]: https://docs.gradle.com/enterprise/api-manual/#2025_1 [3]: 2024.3.0...d13269e#diff-5f0f82d225c2ea054223a09b86f6069c57a4f23b7521c846f46e92c71c48cc6e 🚨 **Breaking changes** - **Added**: Many new API endpoints and features from the Develocity 2025.1 API spec (see [API changelog][2]). - **Removed**: 🚨 The library no longer bundles an SLF4J implementation. While bundling one was convenient for logging in scripts, it would create conflicts when a different implementation was provided. Users must now provide their own logging backend if needed. See the [logging documentation][4] (#332). - **Changed**: 🚨 Configuration is now aligned with official Develocity tooling, simplifying setup (#468, #455). - The server URL variable is now `DEVELOCITY_URL` (previously `DEVELOCITY_API_URL`) and should be the base URL of your instance (e.g., `https://develocity.example.com`), *without* the `/api/` suffix. The code counterpart is now `Config.server` (previously `Config.apiUrl`). - The access key variable is now `DEVELOCITY_ACCESS_KEY` (previously `DEVELOCITY_API_TOKEN`) and must be in the `host=key` format. The code counterpart is now `Config.accessKey` (previously `Config.apiToken`). - Conventional access key locations (e.g., `~/.gradle/develocity/keys.properties`) are now supported and used by default. See the [access keys documentation][5]. - **Changed**: 🚨 The library no longer implicitly shares HTTP client resources such as connection and thread pools across different `DevelocityApi` instances. This fixes resource closure issues in long-running processes like Gradle daemons. This behavior is preserved for Kotlin Notebooks to optimize resource usage (#451). - **Changed**: The library is now compiled with Kotlin language version 1.8 for broader compatibility, including older Kotlin/Jupyter kernels and the Kotlin version embedded in Gradle (#404, #426). [4]: https://github.com/gabrielfeo/develocity-api-kotlin/blob/main/docs/Logging.md [5]: https://github.com/gabrielfeo/develocity-api-kotlin/blob/main/docs/AccessKeys.md [6]: https://github.com/gabrielfeo/develocity-api-kotlin#setup **Full Changelog from 2024.3.0**: 2024.3.0...2025.1.0

2024.3.0 Generated from the API spec of [Develocity API 2024.3][1]. \## What's Changed ℹ️ This release is equivalent to the last alpha, 2024.3.0-alpha01 (new build of the same commit). \### New API spec - [Develocity API changelog][2] - [Library API diff (see `library.api`)][3] [1]: https://docs.gradle.com/enterprise/api-manual/#reference_documentation [2]: https://docs.gradle.com/enterprise/api-manual/#2024_3 [3]: 2024.2.0...2024.3.0 \### Notable changes - **Added**: many new API endpoints and features (see [API changelog][2]) - **Changed**: documentation improvements (library API) **Full Changelog from 2024.2.0**: 2024.2.0...2024.3.0 **Full Changelog from 2024.3.0-alpha01**: 2024.3.0...2024.3.0-alpha01

Prepare for next release (#353) 

Prepare for next release (#310) 

Prepare for next release (#307) 

Hide LoggerFactory from public API (#294) 

Prepare for alpha release (#281) 

Bump version for next release (#205) 

Fix javadoc missing generated API (#200) Move Dokka configuration to the `jvm-library` plugin, which is applied before `test-suites`, and stop passing a fixed source root for Dokka so that generated API source set is included. Also fix some configuration avoidance smells. When refactoring build logic into plugins, Dokka stopped recognizing the correct source set. #199 fixed this by passing a specific source root to Dokka, but this caused the resulting javadoc to not include the generated API. Bisecting shows that moving the test suite setup (456f769), making test suites be set up before Dokka, was when the issue started.