4 ms·

If 8.1 is only bug fixes and no new backward compatible functionality, then this release should be called 8.0.1 based on your semver link above (not 8.1)

• saghul 9y ago
  Technically correct, but Node tends to err on the safe side, specially when dependencies are bumped, as is the case. In this release both libuv and npm were updated.
• gkya 9y ago
  Node version numbers are weird. I'm not a node user but if this is semver sth. is certainly wrong, I see a major version update every other month here.
  • Vinnl 9y ago
    The previous major version update was in September 2016: https://nodejs.org/en/download/releases/ https://nodejs.org/en/download/releases/
• andrewbarba 9y ago
  8.1 is correct. They introduced new functionality (minor version number) to the inspector. In general Node is very very good at following semver. Even for something as seemingly small as this, it requires the minor number to increment. If you follow along their issues on Github, they always tag PR's as needing a major/minor/patch increment. That way when merged it's really easy to see how the version numbers need to increase, or if they need to wait to merge something.
• Vinnl 9y ago
  The minor improvements are the new backwards-compatible functionality, such as identifying Promise triggers or making fs.Stats times available as numbers. Otherwise yes, you'd be right.