doc: update V8 ABI release policy#64196
Open
RafaelGSS wants to merge 1 commit into
Open
Conversation
Collaborator
|
Review requested:
|
Document the V8-related native addon ABI policy discussed in nodejs/TSC#1852. Starting with Node.js 27, V8 updates may land during Alpha and Current even when they require a `NODE_MODULE_VERSION` bump, as long as the ABI change is documented in release notes. Refs: nodejs/TSC#1852 (comment) Signed-off-by: RafaelGSS <rafael.nunu@hotmail.com>
RafaelGSS
force-pushed
the
drop-abi-stability-v27
branch
from
7f68146 to
2b05131
Compare
aymen94
approved these changes
Jun 30, 2026
aduh95
reviewed
Jun 30, 2026
Comment on lines
+1382
to
+1395
| 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. |
Contributor
There was a problem hiding this comment.
Why is this limited to V8? What does it mean for ABI stability for Node.js-specific native APIs?
Also I'm not sure we have consensus for freezing ABI when entering LTS, IIRC there was interest in backporting ABI-breaking changes to LTS as well
aduh95
reviewed
Jun 30, 2026
Comment on lines
+1390
to
+1391
| permitted in exceptional cases such as security fixes. They are not permitted | ||
| in Maintenance releases. |
Contributor
There was a problem hiding this comment.
As of Node.js 27, we no longer have a Maintenance status
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Document the V8-related native addon ABI policy discussed in nodejs/TSC#1852.
Starting with Node.js 27, V8 updates may land during Alpha and Current even when they require a
NODE_MODULE_VERSIONbump, as long as the ABI change is documented in release notes.Refs: nodejs/TSC#1852 (comment)
@nodejs/tsc @nodejs/releasers