Skip to content

doc: add experimental modules lifetime policy #62753

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 2 commits into from
Apr 18, 2026
+8 −0
Merged

doc: add experimental modules lifetime policy #62753

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
36a27fe
doc: add experimental modules lifetime policy
ShogunPanda Apr 18, 2026
15bdd13
fixup
ShogunPanda Apr 18, 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
8 changes: 8 additions & 0 deletions doc/contributing/collaborator-guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -462,6 +462,14 @@ For pull requests introducing new core modules:
* Land only after sign-off from at least two TSC voting members.
* Land with a [Stability Index][] of Experimental. The module must remain
Experimental until a semver-major release.
* Introducing an Experimental feature means taking ownership of the experiment
and committing to a clear outcome: either promoting it to stable or removing
it in a timely manner. Because experimental features can be vulnerable to
security issues, the author is also expected to help assess and patch
vulnerabilities. If an experimental feature has reached mainstream adoption such
that breaking changes are not realistically possible without ecosystem breakage,
it should be considered stable and either be promoted or be removed after a
deprecation cycle.

### Introducing new APIs on the global scope

Expand Down
Loading