How to use
- Start after the dependency and impact picture already looks believable enough that the next question is controlled removal, not discovery.
- Enter consumer spread, package spread, alias window, docs readiness, warning channel, and migration status.
- Read the output as a staged deprecation note, not as a substitute for the real repository policy.
Plan the deprecated path before rollout starts
This page fills the gap between “I know the blast radius” and “I know how to retire the old token safely.”
How to choose between nearby pages
Use Token Impact Simulator when the question is still what changes first. Use Token Rollout Checklist when the deprecation path is already clear and the remaining question is pre-merge or pre-release checks. Use this page in the middle, when you still need to define alias grace, warning timing, and hard removal order.
FAQ
What does this page organize?
It turns token change type, consumer spread, alias window, docs, warnings, and migration state into a staged deprecation plan before hard removal.
When should I use this instead of Token Rollout Checklist?
Use Token Rollout Checklist when the change is already heading toward merge or rollout. Use this page earlier, when the open question is how long to keep aliases, when to freeze new writes, and when hard removal becomes safe.
Does this replace repository-specific deprecation policy?
No. It is a general planning page and should be combined with the actual repository policy, release cadence, and migration requirements.
What is stored in the share URL?
The share URL stores change type, release stage, alias window, consumer count, package count, docs readiness, warning channel, migration status, and target token.