Commit fe91868982e for nodejs

commit fe91868982e94a0f1a543ec8c89f590a3865d783
Author: Joyee Cheung <joyeec9h3@gmail.com>
Date:   Sat Oct 31 13:01:56 2026 +0100

    doc: clarify that V8 major upgrade uses stable release

    Along with Chrome, V8 has several different release channels. A
    V8 release only reaches stable after the stable cut has been rolled
    out and tested in several Chrome release channels, where regressions
    and bugs are discovered and fixed.

    This patch clarifies that we follow the _stable release_ of main
    branch to reduce the amount of churn needed. The V8 stable releases
    are already battle tested in Chrome and generally contain fewer
    regressions/bugs that would require another refresh to address.

    Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
    PR-URL: https://github.com/nodejs/node/pull/67106
    Reviewed-By: Chengzhong Wu <legendecas@gmail.com>
    Reviewed-By: Gürgün Dayıoğlu <hey@gurgun.day>
    Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
    Reviewed-By: Richard Lau <richard.lau@ibm.com>
    Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
    Reviewed-By: Tierney Cyren <hello@bnb.im>
    Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
    Reviewed-By: Ulises Gascón <ulisesgascongonzalez@gmail.com>

diff --git a/doc/contributing/maintaining/maintaining-V8.md b/doc/contributing/maintaining/maintaining-V8.md
index f5eb6faac23..880a06425d0 100644
--- a/doc/contributing/maintaining/maintaining-V8.md
+++ b/doc/contributing/maintaining/maintaining-V8.md
@@ -327,8 +327,15 @@ Revision_ from the 5.4 branch that can be useful in the update process above.

 ### Major updates

-We upgrade the version of V8 in Node.js `main` whenever a V8 release goes stable
-upstream, that is, whenever a new release of Chrome comes out.
+Along with Chrome, V8 has several
+[different release channels](https://chromium.googlesource.com/chromium/src/+/lkgr/docs/process/release_cycle.md).
+A V8 release only reaches stable after the stable cut has been rolled out and tested
+in several Chrome release channels, where regressions and bugs are discovered and fixed.
+
+In the Node.js `main` branch, we typically upgrade the version of V8 whenever a
+release of V8 finishes stable promotion and a _stable release_ is out.
+The schedule of V8 release cycles can be found
+[here](https://chromiumdash.appspot.com/schedule).

 V8 updates can require a `NODE_MODULE_VERSION` bump if they change the native
 addon ABI. See the release process documentation for when