We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
A few packages in plasmicpkgs (plasmic-cms, react-scroll-parallax,lottie-react for example) use 0.0.x for their version.
This leads to updates always indicating a major breaking release. This makes it harder to update them automatically via tooling.
Is there a reason not to use 0.x.y (or even x.y.z) for them to distinguish between major an minor upgrades?
As far as I can tell plasmicpkgs versions are automatically bumped, so it is probably hard to distinguish between major and minor upgrades?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
A few packages in plasmicpkgs (plasmic-cms, react-scroll-parallax,lottie-react for example) use 0.0.x for their version.
This leads to updates always indicating a major breaking release. This makes it harder to update them automatically via tooling.
Is there a reason not to use 0.x.y (or even x.y.z) for them to distinguish between major an minor upgrades?
As far as I can tell plasmicpkgs versions are automatically bumped, so it is probably hard to distinguish between major and minor upgrades?
The text was updated successfully, but these errors were encountered: