Explicit release IDs and safer schema management

Published: August 10, 2026

v2.28.0

New Features

  • create_release tool: Now accepts an optional releaseId parameter. If omitted, an ID is generated.

Improvements

  • Schema tools: Clarified that MCP-managed and Studio-managed schemas must use separate workspace names, and that get_schema always resolves an MCP-managed workspace to its MCP-managed schema.

Fixes

  • deploy_schema tool: Now always refuses to write to a workspace with a Studio-deployed schema, even when a stale MCP-managed row already exists for that workspace. This prevents further MCP mutations to a Studio-managed workspace.

Related documentation

Loading...