-
Notifications
You must be signed in to change notification settings - Fork 225
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
If you're going to make backwards-compatible breaking changes to your API, you need to increment more than the patch version #46
Comments
Can you explain the issue? It was not meant to be a breaking change, apologies for the time wasted. |
The only thing I did was try to create a new yarn.lock file and wound up with this stack trace:
Downgrading to the release from yesterday(?) fixed it. Here's the call site:
|
Apologies, i will fix this now! |
Thanks, sorry for venting, it was extremely frustrating to have a build break at deployment and have no idea why and it took a while to figure it out. |
No problem - I have fixed the issue now. Any problems let me know. |
My builds broke because you do not follow semver.
Please follow semver.
Another breakage and I will drop your package and use something else. It's not a hard standard to follow and wasting a bunch of others' time because you're too lazy is really rude.
The text was updated successfully, but these errors were encountered: