GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
I dont see a reason to keep a "0" build number when you increment a patch or higher. Keeps the version cleaner especially when you use "npm version" before a release.
npm version patch returned 1.2.4-0
npm version patch
npm version patch returns 1.2.4
drop zeroed build number
"Build number" no longer exists. Moving to a spec that's closer to https://github.com/mojombo/semver in 2.0.
chore(build): ensure zero build number does not remain after incremen…
…ting version (npm/node-semver#29)