Skip to main content

Component Version Migration

Migrate consuming applications from v1 to v2 of component library with deprecation warnings, codemods, and rollout plan.

Complexity: Complex | Duration: 30m+ | Category: Creative/Design

Tags: migration versioning breaking-changes codemods

Workflow Diagram​

Steps​

Step 1: Document breaking changes​

Agent: design

systems-architect - changelog

Step 2: Create migration guide​

Agent: technical

writer - upgrade instructions

Step 3: Develop automated codemods​

Agent: frontend

developer - code transformation

Step 4: Add deprecation warnings to v1​

Agent: frontend

developer - developer notifications

Step 5: Test migrations in sample apps​

Agent: qa

analyst - validation

Step 6: Coordinate with consuming team​

Agent: design

systems-architect - rollout planning

Step 7: Monitor adoption metrics​

Agent: data

analyst - migration tracking

Usage​

To execute this workflow:

/workflow creative/design/component-version-migration.workflow

See other workflows in this category for related automation patterns.