From 117785941554edea5e7d470bb6626ebc3fe6d29c Mon Sep 17 00:00:00 2001 From: Benjamin Gruenbaum Date: Wed, 19 Jun 2024 20:01:21 +0300 Subject: [PATCH] meta: warnings bypass deprecation cycle Allow for emitting new warnings (in particular, in case of developer bugs) without going through a deprecation cycle. Co-authored-by: Antoine du Hamel --- doc/contributing/collaborator-guide.md | 1 + 1 file changed, 1 insertion(+) diff --git a/doc/contributing/collaborator-guide.md b/doc/contributing/collaborator-guide.md index 43adfbb8a272ba..d077cb5e651722 100644 --- a/doc/contributing/collaborator-guide.md +++ b/doc/contributing/collaborator-guide.md @@ -356,6 +356,7 @@ Existing stable public APIs that change in a backward-incompatible way must undergo deprecation. The exceptions to this rule are: * Adding or removing errors thrown or reported by a public API. +* Emitting a runtime warning. * Changing error messages for errors without error code. * Altering the timing and non-internal side effects of the public API. * Changes to errors thrown by dependencies of Node.js, such as V8.