TypeScript SDK OpenAPI-generated types
The TypeScript SDK 3.0 and 4.0 releases now derive core response and streaming contracts from Runtype's committed OpenAPI spec, removing stale hand-written entity shapes.
@runtypelabs/sdk 3.0 and 4.0 moved the core TypeScript contracts onto the same committed OpenAPI spec that powers the API reference. Streaming events and entities such as Prompts, Users, Integrations, Flows, Flow Steps, Tools, Records, Surfaces, Schedule Runs, Provider Keys, and Built-In Tools now use spec-derived types instead of hand-maintained mirrors.
The change is intentionally a major version series because TypeScript now catches fields that were already absent on the wire: for example, stale flow status fields, over-declared metadata summaries, and the nonexistent tools.getExecutions() endpoint. Runtime responses did not become stricter — the SDK stopped promising shapes production never returned.
This keeps Dashboard, CLI, API docs, and SDK consumers anchored to one source of truth: fix the route schema, regenerate the spec-derived artifacts, and the SDK follows.