fix(documentation): update all supported node version in README.md

[arnaud-zg]

Linked issue #27

[danhunsaker]

Minor sorting issue to resolve - comments inline - and only one other issue. Please, here and in your boxfile.ymls, drop the revision number from all version strings. Major and minor are plenty for Node; some things only need the major. Most things shouldn't include a version number at all, but Node isn't one of them.

Anyway. Drop the revision parts of all the versions here, fix the sorting, and otherwise it looks good from here.

[danhunsaker]

Still need to drop revision numbers, but the sort looks better.

[arnaud-zg]

Hum, what do you mean by drop revision numbers. I just checked, there is no package.json or CHANGELOG file in this repository.

[danhunsaker]

Version numbers for Semantic Verisoned projects, like Node, consist of a few parts. Namely, {Major}.{Minor}.{Revision}.{Patch}-{Tag}, where you can drop any component as long as you also drop the ones after it, though Patch is often omitted entirely anyway unless there's a hotfix.

The Nanobox packages for NodeJS include Major, Minor, Revision, and sometimes Tag values in their version numbers, but boxfile.yml configurations should not, so we intentionally leave out Revision (and Tag) values in the documentation.

[arnaud-zg]

Got it, so actually I don't need to do anything on this pull request.

[arnaud-zg]

About versioning, I actually use this package for my personal project. It can be a great idea to add it to this repository.

• https://github.com/conventional-changelog/standard-version

[danhunsaker]

@arnaud-zg Um, no, that's not what I was saying at all. Where you have 0.8.28 and 0.10.40, it should just be 0.8 and 0.10.

Is that clearer?

[arnaud-zg]

Ooh okay, it's done. 😸

[danhunsaker]

Looks great!

[CruiseMan]

@danhunsaker Lets merge it, we need it

[arnaud-zg]

Any news ?