Sure; nothing in

semver

would stop you from a continuous release cycle. There's a section on that page titled "Why Use Semantic Versioning", but here are mine off the cuff: Pros: * Easy to automate; most package managers, like

npm

, have built-in semver management tools that will automatically tick up your version number for you * Highly recognizable standard, especially in the JavaScript world * Very flexible standard, allows for lots of metadata to be concisely displayed (e.g. `2.0.0-beta+20170816123155`: The beta version of major release 2 was released on 8/16/2017 at 123155 pm) * You don't have to remember the date you released something to go find that release Cons: * Your boss made a different decision