deprecation-and-migration

To plan an API deprecation without breaking consumers, generate a staged migration plan that includes compatibility bridges, dual-run strategies, or shims. This approach classifies the change impact and documents ordered migration steps to ensure old and new paths remain functional.

A staged migration plan for removing deprecated commands or configs is a structured rollout strategy that finds real consumers, documents the change, and specifies verification commands. It requires consumer evidence and defines measurable removal criteria before the old surface is fully retired.

To verify a schema migration is complete, run defined verification commands that prove both old and new surfaces work. The migration plan returns a BLOCKED or PARTIAL status when consumer evidence is missing, ensuring removal criteria are measurably met before completion.

Yes, you can use a dual-run strategy to sunset a workflow across code, docs, and registry artifacts. This migration approach applies compatibility bridges and shims across multiple artifact types, preserving rollback capabilities while requiring consumer evidence before final removal.

The best way to classify changes when renaming an API is to evaluate the impact on real consumers and categorize the change as additive, deprecating, breaking, or removal. This classification directly shapes the staged migration plan, communication rollout, and rollback strategy.

A migration plan returns a BLOCKED status during release planning when consumer evidence is missing or verification commands fail to prove both old and new paths work. This mechanism prevents unsafe removals by requiring measurable removal criteria and documented impact classification before proceeding.