meta: warnings bypass deprecation cycle

Allow for emitting new warnings without going through a deprecation
cycle.

Co-authored-by: Antoine du Hamel <[email protected]>
PR-URL: #53513
Reviewed-By: Matteo Collina <[email protected]>
Reviewed-By: Geoffrey Booth <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Yagiz Nizipli <[email protected]>
Reviewed-By: Trivikram Kamat <[email protected]>
Reviewed-By: Chengzhong Wu <[email protected]>
Reviewed-By: Marco Ippolito <[email protected]>
Reviewed-By: Rafael Gonzaga <[email protected]>
Reviewed-By: Moshe Atlow <[email protected]>

Author: benjamingr

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.