Gar
If you want to independently add the `release` type with tests go for it. I was just adding it in a discrete commit while I was in here.
This seems very discrete and user-friendly. So the idea is that npm could then support `npm version release`? One of the biggest lessons I've learned in maintaining npm is that...
`if (!this.prerelease.length) {` I should hope, right?
```javascript > (new (require('.').SemVer)('1.0.0')).inc('release') Uncaught Error: version 1.0.0 is not a prerelease at SemVer.inc (classes/semver.js:181:17) > require('.').inc('1.0.0', 'release') null ``` please remember that `semver.inc` catches errors, only the semver object...
Draft PR at https://github.com/npm/node-semver/pull/752
Added a link to this in the [v11 roadmap](https://github.com/npm/statusboard/issues/488). This would be a breaking change. I also like that it suggests just erroring instead of trying to come up with...
> I personally am rather against this. This adds just way too much complexity to what should be a bare-bones setup. 100% agree here. This is currently solving one valid...
> no carve out for special behavior on pre-1.0.0" right Yes. We are only looking for pre-release tags here. They are a VERY clear signal that this is not a...
Great summary @kytta
> However, I feel the shitposting urge Please don't do this. Consider this your final [code of conduct](https://docs.npmjs.com/policies/conduct) warning