Skip to content

doc: allow deprecations while a release is Current #64387

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mcollina wants to merge 1 commit into
base: main
Choose a base branch
from
+10 −4
Open

doc: allow deprecations while a release is Current #64387

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 10 additions & 4 deletions doc/contributing/collaborator-guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -539,12 +539,18 @@ example, due to removal of an End-of-Life deprecated API).

<a id="deprecation-cycle"></a>
A _deprecation cycle_ is a major release during which an API has been in one of
the three Deprecation levels. Documentation-Only Deprecations can land in a
minor release. They can not change to a Runtime Deprecation until the next major
release.
the three Deprecation levels. A deprecation can be added to a release line at
any point while that release line is Current, but not once it has entered the

@avivkeller avivkeller Jul 10, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

at any point

Surely not a patch, however?

Active LTS or Maintenance phases. A deprecation added while a major release is

@aduh95 aduh95 Jul 9, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Those phases are going away, Node.js 27 won't have "Active LTS" not "Maintenance" phases

Current counts as a deprecation cycle for that release: the API can change to
the next deprecation level in the following major release. Documentation-Only
Deprecations can land in a minor release. They can not change to a Runtime
Deprecation until the next major release.

No deprecated APIs can change to End-of-Life without going through a Runtime
Deprecation cycle. There is no rule that deprecated code must progress to End-of-Life.
Deprecation cycle. An API that received a Runtime Deprecation while a major
release was Current can be removed (End-of-Life) in the following major
release. There is no rule that deprecated code must progress to End-of-Life.
Documentation-Only and Runtime Deprecations can remain in place for an unlimited
duration.

Expand Down
Loading