Release History

[NEW] Generating a support bundle now requires the management API token. Previously, any caller able to reach the Develocity namespace over the cluster network could generate and download a bundle without credentials. Standard installations already provision this token, so there is nothing for you to configure.

[NEW] develocityctl support-bundle --include-usage adds the last 180 days of usage records to the bundle, so you can send them to Gradle support along with everything else it collects. These records identify people by email address and username, and name the repositories and products they used, so the option is off by default. It requires Develocity 2026.2.3 or later.

[FIX] develocityctl backup restore now restarts only the components that use the application database. Monitoring, the proxy, the Develocity Operator, Edge nodes and the MCP server stay up for the whole restore, so you keep monitoring coverage and less of Develocity goes offline while it runs.

[NEW] Admin commands uses port-forward instead of kubectl exec when management API token is available

[FIX] This maintenance release focuses on stability and security by incorporating dependency updates.

[NEW] The system reset-system-password command is adjusted for new version for Develocity

[FIX] Stability and security improvement by incorporating dependency updates

[NEW] config-file upgrade - upgrades unattended configuration files to any version (latest or specific one)

[NEW] Support-bundle generation supports including build-insight metrics

[NEW] Commands system get-default-system-password and system reset-system-password now display warnings when unattended configuration may have been used.

[FIX] This maintenance release focuses on stability and security by incorporating dependency updates.