Recipe catalog / breaking-change-signal
Detect breaking changes
Does change indicate a change that would break existing callers, integrations, stored data, or documented behavior?
You need to flag changes that require a major version bump, a migration note, or downstream coordination before they merge.
Explore this recipe interactively ยท Source and implementation guide
Use breaking-change-signal in TypeScript
Install with npm install jev-recipes. Requires Node.js 22.9 or newer and ES modules. Set TYPESAFE_API_KEY in your server environment for live calls, which send input to TypeSafe and use API quota. See the installation guide.
import { breakingChangeSignal } from 'jev-recipes/breaking-change-signal';
const result = await breakingChangeSignal({
"change": "Rename the userId field in the /v1/orders response to customerId and remove the deprecated legacyStatus field from the same payload.",
"context": "Public REST API consumed by three partner integrations and the mobile app.",
"minConfidence": 0.8
});
console.log(result);
Input contract
| Field | Type | Needed |
|---|---|---|
| change | string | Required |
| context | string | Optional |
| minConfidence | number | Optional |
Full input and result schemas
{
"input": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {
"change": {
"type": "string"
},
"context": {
"type": "string"
},
"minConfidence": {
"type": "number",
"minimum": 0,
"maximum": 1
}
},
"required": [
"change"
]
},
"result": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {
"model": {
"type": "string"
},
"usage": {
"type": "object",
"properties": {
"input_tokens": {
"type": "integer",
"minimum": 0,
"maximum": 9007199254740991
},
"output_tokens": {
"type": "integer",
"minimum": 0,
"maximum": 9007199254740991
}
},
"required": [
"input_tokens",
"output_tokens"
],
"additionalProperties": false
},
"status": {
"type": "string",
"enum": [
"ready",
"review"
]
},
"probability": {
"type": "number",
"minimum": 0,
"maximum": 1
},
"confidence": {
"type": "number",
"minimum": 0,
"maximum": 1
},
"verdict": {
"type": "string",
"enum": [
"breaking",
"compatible"
]
}
},
"required": [
"model",
"usage",
"status",
"probability",
"confidence",
"verdict"
],
"additionalProperties": false
}
}Saved example result
This hand-authored response demonstrates the contract. It is not a model accuracy measurement. Run it without an API key: npx jev-recipes demo breaking-change-signal.
{
"model": "demo-fixture",
"usage": {
"input_tokens": 0,
"output_tokens": 0
},
"status": "ready",
"probability": 0.95,
"confidence": 0.95,
"verdict": "breaking"
}
Evaluation evidence
No verified live accuracy measurement is available. Evaluate representative cases before using this decision in your workflow.
Use the evaluation guide to measure this decision on your own labeled cases.
Limitations
- Judges the change as described, not the actual code or its consumers. It cannot know which fields callers really depend on.
- Does not choose a version number or write migration notes. Semantic versioning policy belongs in application code.
Related recipes
- change-meaning: Use change-meaning to decide whether an edit to documentation or contract text alters its meaning.
- instruction-conflict: Use instruction-conflict when a change may disagree with an existing documented rule or requirement.