You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@chaddotson " With v0.8, v0.10, v0.11, v0.12 (commonly casually pronounced 8, 10, 11 and 12), we have grown accustomed to Node.js’s pre-1.0 versioning. So much so that they are frequently referred to dropping the 'zero dot'. " doc here : https://medium.com/@nodesource/node-js-is-semver-8b3938ae8d24
Yes, the node package fully embraces npm's semantic versioning. Current actively LTS is node v8.x.x , conducting semver patch releases monthly and other minor semver releases quarterly.
Semver also has a provision for pre-release tags and these will be released from the Master Node.js branch.
Activity
ppkt commentedon May 25, 2018
@chaddotson this package relies on official semantic versioning document: https://semver.org/
If node follows the same rules, this package is compatible (and by looking on documents: https://docs.npmjs.com/getting-started/semantic-versioning it is). However this package does not support node-specific matching syntax, see #25.
vp93 commentedon May 27, 2018
@chaddotson " With v0.8, v0.10, v0.11, v0.12 (commonly casually pronounced 8, 10, 11 and 12), we have grown accustomed to Node.js’s pre-1.0 versioning. So much so that they are frequently referred to dropping the 'zero dot'. " doc here : https://medium.com/@nodesource/node-js-is-semver-8b3938ae8d24
Yes, the node package fully embraces npm's semantic versioning. Current actively LTS is node v8.x.x , conducting semver patch releases monthly and other minor semver releases quarterly.
Semver also has a provision for pre-release tags and these will be released from the Master Node.js branch.