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

Golang Agent

2026 Release Notes

Version
Date
Changes

2.0.235

June 29, 2026

Resolved Issues:

  • Prevented unit test runs from hanging when the agent is unable to open a test execution. The agent now retries opening the execution in the background and fails open, allowing tests to continue running instead of blocking.

2.0.233

June 4, 2026

Resolved Issues:

  • Addressed security vulnerabilities.

2.0.232

May 19, 2026

New Features and Updates:

  • Added support for the SL_TAGS env var to tag agents for identification in the Cockpit Live Agents Monitor.

  • Contents of the .slignore file are now surfaced in Cockpit Build Insights.

  • Added new parameters to tune coverage data collection and transmission in Light Mode, with improvements to how data is sent to the SeaLights Collector.

Resolved Issues:

  • Improved reliability of remote configuration handling.

2.0.225

April 7, 2026

New Features and Updates:

  • Introduced the fullTestName parameter for Ginkgo to improve test identification and reporting.

2.0.224

March 30, 2026

Resolved Issues:

  • Addressed security vulnerabilities.

2.0.222

March 12, 2026

New Features and Updates:

  • Added console message output for CLI commands.

  • Introduced new CLI flags to control logging behavior:

    • --logLevel

    • --logFile

    • --quiet to suppress console messages.

  • Updated default logging behavior so logLevel is now set to none by default.

  • Standardized CLI flags to use camelCase as the primary format while maintaining backwards compatibility with previous flag names.

  • Optimized default parameter values for improved usability.

  • Added support for the following parameters:

    • testProjectId

    • targetTestProjectId

    • prId

  • Added HTTP retry capability and introduced the failOnError parameter.

  • Added validation to detect when a build submission already exists.

Resolved Issues:

  • Fixed an issue where the go list command could hang during the scan stage.

  • Updated build configuration validation to allow a minimum length of 1 character instead of 3.

  • Fixed an issue where CLI flags were treated as case-sensitive.

  • Fixed environment variable handling so both SEALIGHTS_ and SL_ prefixes work correctly in CLI and runtime environments.

  • Fixed an issue where configuration flags were not applied to embedded instrumentation.

2.0.220

February 26, 2026

Resolved Issues:

  • Addressed a security vulnerability GO-2026-4337 / CVE-2025-68121.

2.0.217

January 5, 2026

Resolved Issues:

  • Fixed an issue with TestMain handling when tests used non-standard variable names.

2025 Release Notes

Version
Date
Changes

1.1.195

May 26, 2025

Resolved Issues:

  • Fixed an issue with the opening and closing of stage executions when using the Godog testing framework.

  • Fixed an issue where argv details from the scan command were missing in the Cockpit Build Monitor.

1.1.192

March 31, 2025

New Features and Updates:

  • Added support for a "none" logging level, allowing logs to be fully suppressed when configured through environment variables.

  • Introduced the SEALIGHTS_IGNORE_GO_TESTS environment variable to disable SeaLights instrumentation for Go tests when needed.

Resolved Issues:

  • Fixed an issue where Test Selection was not properly ignored when the environment variable SEALIGHTS_TEST_SELECTION was set to false.

1.1.184

March 5, 2025

New Features and Updates:

  • Reduced the amount of Git history fetched during scanning to the most recent 5 commits to improve performance.

Resolved Issues:

  • Fixed an issue in Git commit history processing that caused the error: Git scan failed: failed to iterate commits: object not found.

1.1.179

February 5, 2025

New Features and Updates:

  • Added support for Spec tests written using Ginkgo’s Domain-Specific Language (DSL).

1.1.177

January 30, 2025

Resolved Issues:

  • Fixed an issue where Git links were incorrectly generated in the Dashboard.

  • Fixed an issue where incorrect file paths produced by the scan command caused false code change detection.

Last updated

Was this helpful?