@@ -1384,16 +1384,17 @@ 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.
+documented in the release notes.
 
 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.
+when there is no way to make the change without breaking the ABI. Breaking
+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,
+and should be reworked as non-breaking changes before they could land. In
+practice, this means V8 is generally stable on a release line after it enters
+LTS, and no ABI or API breaking changes
+are expected unless in exceptional circumstances.
 
 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