Skip to content

doc: clarify that features cannot be both experimental and deprecated #62456

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

Merged
nodejs-github-bot merged 4 commits into from
Mar 31, 2026
Merged

doc: clarify that features cannot be both experimental and deprecated #62456

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
92cb53a
doc: clarify that features cannot be both experimental and deprecated
aduh95 Mar 27, 2026
44572ae
fixup! doc: clarify that features cannot be both experimental and dep…
aduh95 Mar 27, 2026
2cbc6bb
fixup! doc: clarify that features cannot be both experimental and dep…
aduh95 Mar 31, 2026
0560e80
fixup! doc: clarify that features cannot be both experimental and dep…
aduh95 Mar 31, 2026
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
11 changes: 9 additions & 2 deletions doc/contributing/collaborator-guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -387,6 +387,12 @@ undergo deprecation. The exceptions to this rule are:
* Changes to errors thrown by dependencies of Node.js, such as V8.
* One-time exceptions granted by the TSC.

Experimental and undocumented APIs are not considered stable, therefore are
typically removed without a deprecation cycle. However, if such API has gotten
some non-trivial adoption in the ecosystem, it (or a subset of it) can undergo
deprecation – at which point, changes to that API (or at least, its deprecated
subset) should follow [semantic versioning][] rules.

For more information, see [Deprecations](#deprecations).

#### Breaking changes to internal elements
Expand Down Expand Up @@ -526,8 +532,8 @@ 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.

No API 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.
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.
Documentation-Only and Runtime Deprecations can remain in place for an unlimited
duration.

Expand Down Expand Up @@ -1059,6 +1065,7 @@ need to be attached anymore, as only important bugfixes will be included.
[node-core-utils-issues]: https://github.com/nodejs/node-core-utils/issues
[ppc]: https://github.com/orgs/nodejs/teams/platform-ppc
[s390]: https://github.com/orgs/nodejs/teams/platform-s390
[semantic versioning]: https://semver.org/
[smartos]: https://github.com/orgs/nodejs/teams/platform-smartos
[unreliable tests]: https://github.com/nodejs/node/issues?q=is%3Aopen+is%3Aissue+label%3A%22CI+%2F+flaky+test%22
[windows]: https://github.com/orgs/nodejs/teams/platform-windows
Expand Down
Loading