Feature Lifecycle and Deprecation Policy changedcommunity/feature-lifecycle
Nearest release: v2.1.166, published 2 hours after upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 5 Jun 2026 16:12 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 28 Sep 2026 22:07 UTC.
Upstream edited
Recorded here
Lines+13added
Lines−13removed
From line
22
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits2to this page, all time
The whole hunk
from line 22, old and new numbered
/
from line 22
2222
2323A specification feature is in exactly one of three states:
2424
25| State | Meaning | Implementer expectation |
26| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
27| **Active** | The feature is part of the Current specification revision. | Implement per the feature's normative requirements. |
28| **Deprecated** | The feature remains in the specification but is scheduled for removal. A migration path is documented (see below). | New implementations should not adopt the feature. Existing implementations should migrate before the earliest removal date. |
29| **Removed** | The feature has been deleted from `draft` and will be absent from the next Current revision. It remains documented in the Final revision it last appeared in. | Implementations targeting that next Current revision must not depend on the feature. |
25| State | Meaning | Implementer expectation |
26| - | - | - |
27| **Active** | The feature is part of the Current specification revision. | Implement per the feature's normative requirements. |
28| **Deprecated** | The feature remains in the specification but is scheduled for removal. A migration path is documented (see below). | New implementations should not adopt the feature. Existing implementations should migrate before the earliest removal date. |
29| **Removed** | The feature has been deleted from `draft` and will be absent from the next Current revision. It remains documented in the Final revision it last appeared in. | Implementations targeting that next Current revision must not depend on the feature. |
3030
3131A Deprecated feature MAY be restored to Active by a SEP that supersedes the
3232deprecation SEP and documents the changed circumstances. Restoration follows
from line 140
140140
141141## Roles
142142
143| Action | Who |
144| ---------------------------------------------- | ----------------------------------------------------------------------------------------------- |
145| Propose deprecation, extension, or restoration | Any contributor, per the SEP process |
146| Sponsor | A Maintainer or Core Maintainer, per the SEP process |
147| Approve a deprecation SEP | Core Maintainers, per the [governance decision process](/community/governance#decision-process) |
148| Decide a removal during release preparation | Core Maintainers, per the [governance decision process](/community/governance#decision-process) |
149| Approve an extension or restoration SEP | Core Maintainers, per the [governance decision process](/community/governance#decision-process) |
150| Approve expedited removal | Core Maintainers, per the [governance decision process](/community/governance#decision-process) |
143| Action | Who |
144| - | - |
145| Propose deprecation, extension, or restoration | Any contributor, per the SEP process |
146| Sponsor | A Maintainer or Core Maintainer, per the SEP process |
147| Approve a deprecation SEP | Core Maintainers, per the [governance decision process](/community/governance#decision-process) |
148| Decide a removal during release preparation | Core Maintainers, per the [governance decision process](/community/governance#decision-process) |
149| Approve an extension or restoration SEP | Core Maintainers, per the [governance decision process](/community/governance#decision-process) |
150| Approve expedited removal | Core Maintainers, per the [governance decision process](/community/governance#decision-process) |
151151
152152Lead Maintainers retain veto authority over each of the approvals
153153above, per the [governance roles](/community/governance#roles) definition.
No line in this hunk matches that.