deprecation-and-migration

Removing deprecated APIs safely requires batching the cleanup by blast radius and applying semver-aligned migrations for consumers. This process uses a pre-removal checklist to validate bake duration and replacements before staging isolated removals.

Planning breaking changes migrations involves inventorying affected surfaces and decomposing removals into batches like internal-only changes and runtime API updates. You then create changesets with concrete diff-based migration recipes to verify the update path.

Managing string-union member removals and type alias deletions involves isolating these typed changes into specific blast-radius batches. You run typecheck and lint validation across the batch to catch consumer type errors before generating a semver changeset.

Yes, API deprecation retirement requires changesets for npm package publishing to document the correct semver upgrade path. Post-merge operational validation verifies that the published npm version matches the intended changeset version before closing the epic.

Yes, this deprecation retirement workflow handles public symbol renames and documentation references by sweeping docs during the migration verification loop. The process fits deprecation retirement work involving @deprecated markers across TypeScript and documentation.

You should batch API deprecation removals when handling mixed blast radius scopes like internal-only changes alongside runtime API changes. Splitting removals into isolated batches ensures failures are easier to triage and revert during the migration verification loop.