Commit 49d2d81d1c1 for nodejs

commit 49d2d81d1c1537d7b67e2d7afb01e920bced5245
Author: Antoine du Hamel <duhamelantoine1995@gmail.com>
Date:   Wed Oct 7 16:29:15 2026 +0200

    doc: clarify revert PR label policy

    Signed-off-by: Antoine du Hamel <duhamelantoine1995@gmail.com>
    PR-URL: https://github.com/nodejs/node/pull/66529
    Reviewed-By: Mike McCready <66998419+MikeMcC399@users.noreply.github.com>
    Reviewed-By: Paolo Insogna <paolo@cowtech.it>
    Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com>
    Reviewed-By: James M Snell <jasnell@gmail.com>
    Reviewed-By: René <contact.9a5d6388@renegade334.me.uk>
    Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
    Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
    Reviewed-By: Ulises Gascón <ulisesgascongonzalez@gmail.com>
    Reviewed-By: Chengzhong Wu <legendecas@gmail.com>

diff --git a/doc/contributing/collaborator-guide.md b/doc/contributing/collaborator-guide.md
index 96425ebc088..2d3a24adf38 100644
--- a/doc/contributing/collaborator-guide.md
+++ b/doc/contributing/collaborator-guide.md
@@ -507,8 +507,9 @@ rules. That is OK. Append the reason for the revert and any `Refs` or `Fixes`
 metadata. Raise a pull request like any other change.

 Apply `dont-land-on-v?.x` labels to the revert pull request and to its
-corresponding original pull request,
+corresponding original pull request, remove `semver-*` and `notable-change` labels,
 unless the original pull request has already been backported.
+This avoids cluttering CHANGELOGs with information irrelevant for end users.

 ### Introducing new modules