Skip to content

Commit

Permalink
meta: warnings bypass deprecation cycle
Browse files Browse the repository at this point in the history
Allow for emitting new warnings without going through a deprecation
cycle.

Co-authored-by: Antoine du Hamel <duhamelantoine1995@gmail.com>
PR-URL: #53513
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Geoffrey Booth <webadmin@geoffreybooth.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Yagiz Nizipli <yagiz.nizipli@sentry.io>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Chengzhong Wu <legendecas@gmail.com>
Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com>
Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com>
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
  • Loading branch information
benjamingr and aduh95 committed Jul 16, 2024
1 parent 8aab680 commit 508abfe
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions doc/contributing/collaborator-guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down

0 comments on commit 508abfe

Please sign in to comment.