Specmatic OSS Release Notes

2.46.5 (2026-06-11)

Added an MCP server with tools for mock servers, contract-test execution, and backward-compatibility runs.

Improved backward-compatibility output for external $ref changes by preserving clearer source locations and more structured breakage details.
Improved CTRF and filesystem-based report metadata handling so specification paths remain more reliable in federated and local-file reporting flows.
Reduced delays and timeout risk during DNS resolution when shipped reporting flows connect to Specmatic Insights.

Removed legacy stub-usage, test-coverage, and older HTML coverage report outputs in favor of the newer CTRF and HTML reporting flow.
Improved backward-compatibility CTRF spec-path handling so reported paths are recorded relative to the repository root and remain stable across platforms.
Improved externalized example loading coverage and diagnostics for command and test flows.

Improved backward-compatibility diagnostics by surfacing source locations for a wider range of breaking changes, including XML, composed schemas, params, headers, request bodies, and external references.
Improved OpenAPI example handling for object query parameters, form-urlencoded payloads, parameterized media types, and XML oneOf examples across validation, mocks, and command flows.
Added stronger backward-compatibility coverage for composition-heavy and XML-heavy API definitions.

Added CTRF backward-compatibility report generation with richer per-operation change tracking and status details.

Improved backward-compatibility reporting for multi-spec runs so all checked specs are retained in generated BCC output.
Added WIP-aware backward-compatibility handling so WIP scenarios can appear in reports and console output without being treated like ordinary breaking failures.
Improved change tracking for referenced and recursive schemas so operation-level status is calculated more accurately.