Vladislav Chesnokov
03/04/2026, 10:17 AMVladislav Chesnokov
04/28/2026, 7:53 AMJohn
05/08/2026, 3:20 PMLaura Kassovic
05/28/2026, 9:47 PMLaura Kassovic
06/09/2026, 3:41 AMLaura Kassovic
06/12/2026, 5:40 PMTapchicoma
06/17/2026, 8:06 AMBrice Dutheil
06/19/2026, 9:32 AMBrice Dutheil
06/19/2026, 11:27 AMw: file:///.../buildSrc/build.gradle.kts:110:17: 'fun <T : Any, U : T> NamedDomainObjectContainer<T>.getting(type: KClass<U>, configuration: U.() -> Unit): PolymorphicDomainObjectContainerGettingDelegateProvider<T, U>' is deprecated. Use 'val element = getByName<Type>(name) { }' instead. See the Gradle 9.6 upgrading guide.Brice Dutheil
07/08/2026, 5:23 PMShuvadip Chakraborty
07/22/2026, 5:31 AMShuvadip Chakraborty
07/22/2026, 5:39 AMysb33r
08/12/2026, 10:21 AMpnpm toolchain support, which also makes it very easy to take JS/TS-based tools and run them from Gradle i.e. Antora, Downdoc etc. Because you can allow pnpm to manage node on your behalf, it simplifies things even more. You can declare a set of packages to be associated with a toolchain and then prepare them with an instance of PnpmPrepareTask. You can then execute the appropraite packages from your toolchain using instances of PnpmExecTask (which under the hood calls pnpm exec with all the appropriate parameters and environment variables. This is a model similar to waht the JRubyPrepare and JRubyExec tasks do in the Simplified JRuby plugin suite.
All tasks in this release should be CC-compatible and also work on Gradle 9 (although some of the legacy plugins might raise warnings on Gradle 9.7+).
Docs are at javascript-gradle.ysb33r.org/javascript-ecosystem-gradle-plugin-suite/5.0.0/index.htmlJendrik Johannes
08/12/2026, 8:56 PMLaura Kassovic
08/19/2026, 3:50 PMLaura Kassovic
08/19/2026, 9:23 PMysb33r
08/26/2026, 3:59 AMjavaexec to run different version of Gradle against a test set. Simplistic, raw and rough around the edges it got the job done. Testkit would eventually come along and GradleTest evolved to use that under the hood, making debugging easier and simplify setup for more complex test cases.
Anyhow, after that history tidbit, I am glad to announce the GradleTest 5.0.0 got released today. It comes with three main features.
• Support for using custom JDKs in testing. You can create a test set which uses a JDK other than your other compatibility tests. Let's say you build your plugin against JDK11, but want to test against Gradle9, you can create a second test set where the JDK is set to 17. I_t even comes with the option to perform variant selection when it is needed. (Thanks to some tips from @Vampire)_
• Support for testing a plugin against isolated projects if the Gradle version under test is Gradle 9.7+
• Better customisation of a per-version basis. You can change behaviour depending of the Gradle version under testing including activating or silencing specific deprecation warnings, configuration cache modes and now isolation project modes. The new DSL is a good departure away from the clunky 4.0 DSL for version customisation.
And it has been tested on a host Gradle version range of 7.3 to 9.7.
More info here and hopefully you'll find it useful to test your own plugins.
gradletest.ysb33r.org/gradletest/5.0.0/index.htmlLaura Kassovic
08/31/2026, 8:56 PMysb33r
09/08/2026, 4:53 PMOperatingSystem.
Well, you don't have to suffer. You can have all that information (and more) with the Operating System plugin. It adds an extension called OS.
What's new with the latest release?
• There is a version that you can apply to settings.gradle(.kts)
• If you work with variants you can even obtain the correct values you need for operating system and machine architecture.
• If you need to look up values for OS/Arch for anything other that what Gradle is running on, you can do that do now via getOsTypes() and getArchitectures().
Hope it helps to resolve some pain for some of you. See the link for more details.
os-gradle.ysb33r.org/operatingsystem-gradle-plugin/3.0.1/usage.htmlysb33r
09/11/2026, 2:43 PMysb33r
09/12/2026, 7:00 AMbuild, check and assemble . Although sufficient for smaller projects I have found doing work for a number of organisations that a couple of petterns arise that really need to have additional lifecycle tasks. Having those also means that CI pipeline recipes can be simplified such that the pipelines only have to call the appropriate lifecycle tasks. Build script and plugin authors can then focus on adding the appropriate tasks into these lifecycle tasks.
Anyhow, I finally got fed up, having to recreate similar setups, so I created a lightweight set of plugins that can be reused and hopefully be some standardisation for people. Obviously if you have already done something like this in your organisation, you have no need for this, but if you are building from scratch again or would like for standard, this could be helpful to you.
I've setup it up in such a way that you can take all of the lifecycle tasks, or just a subset. There is seven lifecycle tasks in this release. Feel free to discuss or contribute more if you want.
gradle-lifecycles.ysb33r.org/lifecycle-tasks/1.0.1/tasks.htmlAlex Semin
09/14/2026, 3:36 PMysb33r
09/20/2026, 8:46 AM3.0.0 got released today. Not many changes, but there are some important notes:
• Only bootstraps versions 1.16.0+ of Doxygen.
• Defaults to using version 1.18.0 of Doxygen.
• Is now tested to be compatible with both Isolated Projects (Gradle 9.7.0+) and Configuration Cache.
• Minimum runtime requirements are JDK8 and Gradle 7.3.3
Details here: doxygen-gradle.ysb33r.orgysb33r
09/22/2026, 8:25 PMAlex Semin
09/24/2026, 5:27 PMisolatedProjects right next to `configurationCache`:
gradlePlugin {
plugins {
create("myPlugin") {
id = "io.github.my.plugin"
// ...
compatibility {
features {
configurationCache = true
isolatedProjects = true
}
}
}
}
}
Before enabling Isolated Projects, most users first want to know whether their plugins support it. A declaration answers that on your plugin's page and can help your plugin in search results. Declaring false is useful too -- there's no penalty for it.
All you need is the new Plugin Publish Plugin version, no Gradle upgrade required.
We've also covered it in the Gradle 9.8.0 release notes, out today, and in the user manual:
• Release notes: Declaring plugin compatibility with Isolated Projects on the Plugin Portal
• User manual, with Kotlin and Groovy snippets: Declaring compatibility with Gradle features
• New to Isolated Projects? Start here: Isolated Projects
A few things to know:
• In the Kotlin DSL, compatibility needs `import org.gradle.plugin.compatibility.compatibility`; in Groovy, it's compatibility(it) { ... }.
• While Isolated Projects is incubating, the declaration shows up in the compatibility table on your plugin's page, marked "(Incubating)", but not as a badge at the top yet.
• Isolated Projects constraints may get stricter before the feature is stable, so treat the declaration as something to revisit.
Questions and feedback are welcome here or in #isolated-projectsBenedikt Ritter
10/09/2026, 9:20 AMysb33r
10/23/2026, 10:56 AMincludedir support.
• A fix for gradle-relative-srcdir,
• Reducer support - Reduce an AsciiDoc file and all its includes into a single .adoc file.
• Kramdoc support - Convert Markdown into AsciiDoc.
• Support for secondary sources was added back in.
• revnumber is now automatically added as an attribute, if it is not already set.
You can chain outputs together too. For instance you can take the output from Reducer and feed it to Downdoc which will create a Markdown file from your AsciiDoc source.Marc Philipp
10/24/2026, 1:05 PMsetup-testlens GitHub Action can authenticate via OIDC instead of the job's GITHUB_TOKEN.
✅️ Grant id-token: write, set use-oidc: true, done.
Read more on our blog: testlens.app/blog/…/oidc-authentication-support?…ysb33r
11/17/2026, 10:48 AMorg.asciidoctor.format as plugin to obtain this feature. It reacts to the formatAll lifecycle task if tit exists, but otherwise asciidoctorFormatAll and asciidoctorFormatCheckAll can be called.David Göransson
11/19/2026, 3:44 PM