Commit 7bfa50aa946 for nodejs

commit 7bfa50aa946920dd3131d4c4283f46e0cb7bdcb8
Author: Chengzhong Wu <legendecas@gmail.com>
Date:   Thu Nov 19 14:24:13 2026 -0500

    doc: add verification steps of V8 major upgrades

    Signed-off-by: Chengzhong Wu <cwu631@bloomberg.net>
    PR-URL: https://github.com/nodejs/node/pull/67559
    Reviewed-By: Tierney Cyren <hello@bnb.im>
    Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
    Reviewed-By: James M Snell <jasnell@gmail.com>
    Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
    Reviewed-By: Richard Lau <richard.lau@ibm.com>
    Reviewed-By: Luigi Pinca <luigipinca@gmail.com>

diff --git a/doc/contributing/maintaining/maintaining-V8.md b/doc/contributing/maintaining/maintaining-V8.md
index 880a06425d0..3f3394e5208 100644
--- a/doc/contributing/maintaining/maintaining-V8.md
+++ b/doc/contributing/maintaining/maintaining-V8.md
@@ -354,23 +354,39 @@ above. A better strategy is to
 4. Refloat (cherry-pick) all the patches from list computed in 1) as necessary.
    Some of the patches may no longer be necessary.

-To audit for floating patches:
+To audit for floating patches, use `git node v8 list-patches` with the
+target V8 release line. For example, before upgrading to V8 15.7:

 ```bash
-git log --oneline deps/v8
+cd $NODE_DIR
+git node v8 list-patches --target=15.7
 ```

+It lists every V8 patch floated since the last V8 import, and whether the
+target line already contains each one. See [`git-node-v8-list-patches`][] for
+how to read the output.
+
 To replace the copy of V8 in Node.js, use the [`git-node`][] tool. For example,
-if you want to replace the copy of V8 in Node.js with the branch-head for V8 5.1
-branch:
+if you want to replace the copy of V8 in Node.js with the branch-head for V8
+15.7 branch:

 ```bash
 cd $NODE_DIR
-git node v8 major --branch=5.1-lkgr
+git node v8 major --branch=15.7-lkgr
 ```

 This should be followed up with manual refloating of all relevant patches.

+After refloating, run `list-patches` on the upgrade branch to verify the
+result:
+
+```bash
+git node v8 list-patches --base=HEAD --check-diff
+```
+
+Check that the listed patches match the ones the earlier run marked to refloat,
+and that each cherry-pick's diff matches its upstream commit.
+
 ## Proposal: Using a fork repository to track upstream V8

 The fact that Node.js keeps a vendored, potentially edited copy of V8 in deps/
@@ -419,6 +435,7 @@ This would require some tooling to:
 [V8TemplateUpstreamBug]: https://bugs.chromium.org/p/v8/issues/entry?template=Node.js%20upstream%20bug
 [`@node-core/utils`]: https://github.com/nodejs/node-core-utils#Install
 [`git-node-v8-backport`]: https://github.com/nodejs/node-core-utils/blob/main/docs/git-node.md#git-node-v8-backport-sha
+[`git-node-v8-list-patches`]: https://github.com/nodejs/node-core-utils/blob/main/docs/git-node.md#git-node-v8-list-patches
 [`git-node-v8-minor`]: https://github.com/nodejs/node-core-utils/blob/main/docs/git-node.md#git-node-v8-minor
 [`git-node-v8`]: https://github.com/nodejs/node-core-utils/blob/HEAD/docs/git-node.md#git-node-v8
 [`git-node`]: https://github.com/nodejs/node-core-utils/blob/HEAD/docs/git-node.md#git-node-v8