Deprecation Notice Template¶

• Capability or contract: Name and version
• Owner: Named maintainer
• Announcement date: YYYY-MM-DD
• First warning release: vX.Y.0
• Planned retirement: Version and date
• Replacement: Supported alternative or documented rationale

Reason and Impact¶

Explain the user problem, affected commands, schemas, packages, state, integrations, and security or operational impact.

Migration and Rollback¶

Provide previewable migration steps, validation, backups, rollback, compatibility window, and support channels.

Evidence¶

Link adoption analysis, warnings, documentation, tests, compatibility reports, approval, and retirement verification.