Conversation
- Remove gitCommitAll calls from lifecycle tests (CLI doesn't use git) - Improve error handling in git helpers for better CI debugging
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🔄 The Pivot
Before: Contractual was a TypeSpec-first code generation tool for Node.js/TypeScript - generating ts-rest clients and server contracts from
.tspfiles.After: Contractual is now the Buf equivalent for REST, events, and data - a schema lifecycle orchestrator that wraps existing best-in-class tools through a single CLI and declarative config.
🎯 Why This Change?
The original vision was too narrow. Every schema ecosystem (OpenAPI, JSON Schema, AsyncAPI, ODCS) has the same lifecycle needs:
But only Protobuf has complete tooling (Buf). Everything else is fragmented - teams manually wire 4-5 separate tools in CI.
Contractual is now the orchestration layer that doesn't exist.
🏗️ What's New
Single Config, Full Lifecycle
CLI Commands
contractual initcontractual lintcontractual breakingcontractual changesetcontractual versioncontractual statusChangesets Workflow (Adapted from @changesets/cli)
Native JSON Schema Differ
The JSON Schema ecosystem has 150M+ weekly downloads but no production-quality breaking change detection. The JSON Schema organization acknowledged this as the #1 missing capability (GSoC 2026 project accepted).
We built it:
📦 New Package Structure
This is a complete rewrite. The old TypeSpec/ts-rest approach is removed. Contractual is now positioned as the missing orchestration layer for schema contract lifecycle management.