Handle BREAKING CHANGE differently before 1.0.0 - Githubissues

prisma-labs / dripip

Opinionated CLI for continuous delivery of npm packages

100 stars 2 forks source link

Handle BREAKING CHANGE differently before 1.0.0 #31

Closed jasonkuhrt closed 4 years ago

jasonkuhrt commented 4 years ago

What

Use https://github.com/conventional-commits/conventionalcommits.org/pull/214 as a guide on how to implement this feature.

Why

Use-cases for this are abundant but a latest one our team hit is with nexus-prisma: https://github.com/prisma-labs/nexus-prisma/commit/68ed3ccace5aa7482dd124706cc8c96087f720ee#diff-2638cf645b095d407cc87da040e27c20

Right now using dripip would result in publishing a 1.0.0 whereas the last release is:
```
* eb9d125 (tag: v0.7.0-next.1) v0.7.0-next.1
```
and what we actually want is 0.7.0-next.2