Versioning and Deprecation

The current REST API uses the /v1 path. Treat request fields, response fields, error codes, and route semantics as the integration contract.

Build tolerant clients

• Ignore response fields that your client does not use.
• Branch on error codes, not error messages.
• Use tools/list as the current contract for MCP tool names and schemas.
• Pin SDK versions in deployed applications and review release notes before upgrades.

SDK releases

The TypeScript SDK, Python SDK, and CLI release independently. Each package uses semantic versioning. A patch fixes behavior. A minor version adds a compatible surface. A major version can contain a breaking package API change.

API changes

STACK can add endpoints, optional request fields, response fields, error details, and MCP tools without changing the /v1 path. We will document a migration before we remove or change a public contract. No fixed deprecation period applies to all surfaces today.