SDK compatibility and releases
These guides and reference examples target the existing public @testcollab/sdk 3.35.0 package. The CLI examples target @testcollab/cli 1.24.0 and the command-based MCP setup uses @testcollab/mcp-server 1.4.0.
Pin a known version
Section titled “Pin a known version”Use your lockfile in CI. Check method signatures and serialization behavior when moving an existing integration to a different SDK version.
Documentation and package surface
Section titled “Documentation and package surface”The developer site documents a curated public integration surface. Existing SDK exports remain available according to the package version you installed; this site release does not remove them or publish a replacement SDK.
The API reference is rebuilt from the current YAML definitions. A newly documented field may need a newer SDK before the client can serialize or decode it. Check both the reference and the installed SDK when adopting a new field.
Upgrade deliberately
Section titled “Upgrade deliberately”Read package release notes, try the updated SDK in a test project, and exercise your complete workflow before upgrading production automation. Check case/plan IDs, BDD ownership, assignments, execution evidence and region configuration.
Find package releases and source in the SDK repository, CLI repository and MCP server repository.