NODE_MODULE_VERSION bumps on Alpha/Current #1194

Since nodejs/node#64196, V8 updates that bump NODE_MODULE_VERSION may land during the Alpha and Current phases of a release line, as long as the ABI change is documented in the release notes.

This came up while reviewing the v27.0.0-alpha proposal (nodejs/node#67062)

My suggestion is: For v27 keep 27.0.0-pre label throughout the Alpha phase, since alpha builds come from the same tree as main and the NMV can still change before 27.0.0. The 27.0.0 release commit will drop the -pre suffix as usual. This issue is about what happens after that.

Current state

main and v27.x both carry:

{ "modules": 153, "runtime": "node", "variant": "v8_15.6", "versions": "27.0.0-pre" },
{ "modules": 152, "runtime": "node", "variant": "v8_15.5", "versions": "27.0.0-pre" },
{ "modules": 151, "runtime": "node", "variant": "v8_15.2", "versions": "27.0.0-pre" },

The alpha ships NMV 153 and does not change the file. The next bump on main will be labelled 28.0.0-pre.

Questions

1. If a V8 update bumps the NMV on v27.x after 27.0.0 (for example to 155
   in 27.2.0), how should the registry describe 153 and 155? The versions
   field is a free-form string and old entries already use ranges such as
   ">=1.1 <2", so one option is ">=27.0.0 <27.2.0" and ">=27.2.0".
   Another is to keep a single version per entry and allow several entries
   for the same major.

2. Where should the ABI change be called out in the release notes, and
   should the semver-major label stay on the PR once it is backported to a
   Current line as a minor?

Once we agree, I'll send a PR updating releases.md and, if needed, the
registry format.

cc @nodejs/releasers