fixup! doc: update V8 ABI release policy

Signed-off-by: RafaelGSS <rafael.nunu@hotmail.com>

Author: RafaelGSS

doc/contributing/releases.md

@@ -1379,20 +1379,25 @@ in the registry. Also include a change to the registry in your commit to
 reflect the newly used value. Ensure that the release commit removes the
 `-pre` suffix for the major version being prepared.
 
-Starting with Node.js 27, V8 updates may land during the Alpha and Current
-phases of a release line even if they require a `NODE_MODULE_VERSION` bump.
-Such changes should still be labeled as semver-major on the default branch.
-When they are promoted to the release line, they may land in semver-minor
-releases as long as the ABI change is clearly documented in the release notes.
-
-The native addon ABI is frozen when a release line enters LTS. After LTS
-promotion, V8 updates that require a `NODE_MODULE_VERSION` bump are only
-permitted in exceptional cases such as security fixes. They are not permitted
-in Maintenance releases.
-
-This policy applies to addons that depend on the V8, Node.js, or other
-non-Node-API native interfaces. Node-API remains the recommended interface for
-native addons that require ABI stability across Node.js versions.
+Starting with Node.js 27, changes that break the native addon ABI and require
+a `NODE_MODULE_VERSION` bump, such as V8 updates, may land during the Alpha and
+Current phases of a release line. Such changes should still be labeled as
+semver-major on the default branch. When they are promoted to the release line,
+they may land in semver-minor releases as long as the ABI change is clearly
+documented in the release notes. If the change also removes or modifies APIs
+that addons use, so that addons need source changes rather than only a
+rebuild, the release notes should say so.
+
+Once a release line enters LTS, ABI-breaking changes are strongly discouraged.
+They should only land when they are necessary, such as for security fixes, and
+when there is no way to make the change without breaking the ABI. Changes that
+are not necessary for an LTS line, such as adding fields to a struct to expose
+more information in a diagnostic API, do not meet this bar. In practice, this
+means V8 is not updated on a release line after it enters LTS.
+
+This policy applies to addons that depend on V8, Node.js, or other non-Node-API
+native interfaces. Node-API remains the recommended interface for native addons
+that require ABI stability across Node.js versions.
 
 ### Test releases and release candidates