The node versioning system makes no sense to me. They release a new major version and their key highlights sound like minor version changes:<p>> Enabling require(esm) by default for Node.js applications<p>> Removing support for Windows 32-bit systems<p>> Stabilizing the node --run command<p>> Enhancements to the test runner, including glob pattern support for coverage files<p>When Java or especially C# increment major versions, they've added some key language or compiler features, large new standard library changes, or breaking changes of some kind. Node uses major versions to announce what more or less sound like housekeeping. Unless they're just bad at writing blog posts, which it seems like they are. Under "Other notable changes", they have:<p>> [83eb4f2855] - (SEMVER-MINOR) deps: V8: cherry-pick cd10ad7cdbe5 (Joyee Cheung) #52535<p>Which tells me literally nothing about this "notable change", unless I go to the pull request: <a href="https://github.com/nodejs/node/pull/52535">https://github.com/nodejs/node/pull/52535</a><p>> module: implement NODE_COMPILE_CACHE for automatic on-disk code caching #52535<p>Which still doesn't seem like a major version headline feature.<p>Consider this "notable change": <a href="https://github.com/nodejs/node/pull/55086/files">https://github.com/nodejs/node/pull/55086/files</a><p>> doc: add abmusse to collaborators<p>> + * [abmusse](<a href="https://github.com/abmusse">https://github.com/abmusse</a>) -<p>> + *Abdirahim Musse* <<abdirahim.musse@ibm.com>><p>I'm guessing they're fully relying on semver to generate their changelogs, but they're not providing any convincing reason to upgrade to 23.0.0 other than to remain up to date as an inherent virtue