プロンプト

Plan a breaking API version change

Plans a breaking API version change with a deprecation timeline, compatibility shims, a client migration guide and adoption telemetry. Use before changing anything clients rely on.

プロンプト全文

English
Help me plan a breaking API version change.
Inputs: current api; changes; clients.

1. Map contract changes and affected consumers.
2. stage coexistence, compatibility checks and migration.
3. define deprecation communication, monitoring and recovery.

Deliver: Change classification, Avoid the break, Versioning, Compatibility layer, Timeline, Telemetry, Client migration guide.
Clarify critical gaps, separate facts from assumptions, and do not invent data, citations or completed actions.

My material: [fill in here]

事前準備

Provide current api; changes; clients.

出典とライセンス

Hodios · Plan a breaking API version change

gabrielanhaia

CC0-1.0