Opening this to discuss whether we should stop treating ABI compatibility changes as blockers for V8 updates in major releases.
We’ve been hitting the same issue repeatedly. v26.0.0 was already delayed for V8 14.6, and that version became outdated almost immediately with Chrome 148 (V8 14.8) going stable.
From the TSC thread, the main pain point is that ABI stability adds pressure and slows down landing V8 updates. Removing that constraint would let updates land when they’re actually ready instead of forcing timing compromises.
There was also the suggestion to drop ABI stability guarantees in majors and push the ecosystem more toward N-API or FFI.
This is probably too late for v26, but could make sense starting in v27.
cc: @targos, who has handled most (if not all) V8 updates for quite a long time
Opening this to discuss whether we should stop treating ABI compatibility changes as blockers for V8 updates in major releases.
We’ve been hitting the same issue repeatedly. v26.0.0 was already delayed for V8 14.6, and that version became outdated almost immediately with Chrome 148 (V8 14.8) going stable.
From the TSC thread, the main pain point is that ABI stability adds pressure and slows down landing V8 updates. Removing that constraint would let updates land when they’re actually ready instead of forcing timing compromises.
There was also the suggestion to drop ABI stability guarantees in majors and push the ecosystem more toward N-API or FFI.
This is probably too late for v26, but could make sense starting in v27.
cc: @targos, who has handled most (if not all) V8 updates for quite a long time