Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Please do not publish backwards incompatible versions with only patch update

See original GitHub issue

You made a patch update from 2.2.0 to 2.2.1 where you removed dist and added src to npm ignore. This now breaks the build on older NPM versions which do not build files automatically.

Patch versions should not be misused like this. This is not even a backward compatible change so you should change major version.

Can you please provide 2.2.2 version where you keep src and dist, and then if you want publish a new version 2.3.0 or even 3.0.0?

Issue Analytics

State:
Created 5 years ago
Reactions:1
Comments:7 (3 by maintainers)

Top GitHub Comments

1reaction

mohsen1commented, Jul 6, 2019

Sorry about this. I can’t unpublish it anymore. Moving forward I will be more thoughtful. Lock files are making this kind of issue happening less.

1reaction

mitarcommented, Aug 15, 2018

Sure, I agree that I could do that, but it worked, and then it broke. Now I have a released version of the package I cannot build documentation anymore for because the new version of this package (I allowed backwards compatible updates) does not allow to build it anymore. 😦

It happens.

Top Results From Across the Web

What is the meaning of "Major Update backward-incompatible ...

The updates have backward-compatible features. green = Patch Update. The updates are just patches to fix bugs, and are backward-compatible.

How to deal with minor and patch releases in pre-1.0 ... - GitHub

For example, is the minor version used for both backwards compatible and backwards incompatible feature changes? Does it not matter whether you update...

Semantic Versioning 1.0.0

Bug fixes not affecting the API increment the patch version, backwards compatible API additions/changes increment the minor version, and backwards incompatible ...

Internet Explorer 11 desktop application ended support for ...

Internet Explorer mode in Microsoft Edge enables backward compatibility and will be supported through at least 2029. Additionally, Microsoft ...

Scala is a Maintenance Nightmare - MungingData

Scala major releases are not backwards compatible. ... Having to bump major versions to release incompatible changes means you'll think ...