For the complete documentation index, see llms.txt. This page is also available as Markdown.

Gradle Plugin

2026 Release Notes

Version
Date
Changes

4.0.1036

September 29, 2026

New Features and Updates:

  • Removed vulnerability by upgrading Jackson to 2.22.3.

4.0.1033

September 18, 2026

New Features and Updates:

  • Upgraded Apache HttpClient to 5.6.4 and Jackson to 2.22.2 to address CVE-2026-68497, sonatype-2026-005959, and CVE-2026-71290.

4.0.1030

August 12, 2026

New Features and Updates:

  • Added support for discovering the .slignore file in the project root directory and passing it to module scanners.

  • Added support for the moduleNamePath flag to report qualified Gradle paths as module names for nested submodules. When moduleNamePath=true, a nested subproject such as :parentA:utils is reported as parentA:utils instead of utils.

  • Updated execution handling to use the SL_LAB_ID environment variable when opening an execution.

  • Removed vulnerabilities in transitive dependencies.

  • Updated the default Gradle plugin version to latest.release when the version is not provided through remote configuration.

  • Fixed a ConcurrentModificationException.

4.0.1020

April 21, 2026

New Features and Updates:

  • Remediated vulnerable dependencies to address security risks.

Resolved Issues:

  • Addressed an issue where opening the test stage failed when multiple test tasks were executed within the same subproject.

  • Corrected a problem where code scanning could be skipped if the agent JAR file was missing.

4.0.1017

March 16, 2026

New Features and Updates:

  • Added support for emitting heartbeat events from the Gradle Plugin process to improve monitoring and execution visibility.

4.0.1014

February 24, 2026

Resolved Issues:

  • Fixed support for testProjectId — setting the testProjectId header when resolving buildSessionId with labId.

4.0.1013

February 9, 2026

Resolved Issues:

  • Fixed an issue encountered while running the pull request configuration command using the Gradle plugin.

4.0.1011

February 3, 2026

New Features and Updates:

  • Prevented duplicate test listeners when configuring test stages per subproject and test task.

  • Added Gradle 9.x compatibility.

2025 Release Notes

Version
Date
Changes

4.0.998

November 11, 2025

New Features and Updates:

  • Added support for configuring a test stage per Gradle subproject and per test task.

4.0.993

August 26, 2025

New Features and Updates:

  • Added additional environment-related logs to improve execution visibility.

4.0.991

August 12, 2025

New Features and Updates:

  • Removed vulnerable dependencies to address security risks.

4.0.990

July 30, 2025

New Features and Updates:

  • Added support for the buildName and branchName parameters in pull request configuration.

4.0.988

June 25, 2025

New Features and Updates:

  • Enhanced resolution of physical paths within buildmaps.

  • Implemented a retry mechanism for dispatching the build-end event.

  • Added support for the testProjectId parameter.

4.0.985

May 20, 2025

New Features and Updates:

  • Added support for using encoded proxy passwords.

  • Added support for using encoded JWT tokens.

2024 Release Notes

Version
Date
Changes

4.0.978

October 26, 2024

New Features and Updates:

  • Upgraded dependent libraries.

4.0.975

October 16, 2024

New Features and Updates:

  • Removed vulnerable dependencies to address security risks.

4.0.969

October 10, 2024

New Features and Updates:

  • Improved Gradle build cache support for multi-module projects. Subprojects containing only integration tests are now fully supported.

4.0.959

July 30, 2024

Resolved Issues:

  • Fixed invalid wrapping of values passed via the testListenerJvmParams parameter.

4.0.954

June 21, 2024

New Features and Updates:

  • Added support for working with the Gradle build cache.

4.0.919

March 07, 2024

New Features and Updates:

  • Removed vulnerable dependencies to address security risks.

4.0.909

February 14, 2024

Resolved Issues:

  • Removed printing of token and buildSessionId values from the console to prevent sensitive data exposure.

Last updated

Was this helpful?