From 508abfe178d7b7a8ee184f7cd094da56203de60b Mon Sep 17 00:00:00 2001 From: Benjamin Gruenbaum Date: Thu, 27 Jun 2024 13:01:23 +0300 Subject: [PATCH] meta: warnings bypass deprecation cycle MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Allow for emitting new warnings without going through a deprecation cycle. Co-authored-by: Antoine du Hamel PR-URL: https://github.com/nodejs/node/pull/53513 Reviewed-By: Matteo Collina Reviewed-By: Geoffrey Booth Reviewed-By: Luigi Pinca Reviewed-By: Michaël Zasso Reviewed-By: Yagiz Nizipli Reviewed-By: Trivikram Kamat Reviewed-By: Chengzhong Wu Reviewed-By: Marco Ippolito Reviewed-By: Rafael Gonzaga Reviewed-By: Moshe Atlow --- 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 e7fc054920b34f..a7021db9b2af48 100644 --- a/doc/contributing/collaborator-guide.md +++ b/doc/contributing/collaborator-guide.md @@ -361,6 +361,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.