-
Notifications
You must be signed in to change notification settings - Fork 397
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
Version 2.1 should be 3.0 #694
Comments
I second this. Also, I really like that there is a documented upgrade path to 2.x but I was unable to find documentation about these breaking changes in 2.1. |
IMO, it is well worth cutting a new release just to get the versioning correct. We lost a half day trying to puzzle out what broke, because we didn't suspect a minor version change would break the entire release process. |
This has been very confusing on our application. Sticking to semver would have been appreciated |
Description of issue
incompatible changes should bump Major version up
2.1.0
According to the Semantic Versioning 2.0 docs, backward incompatible changes should bump major versions up.
Given that
Mix.Release
changing toDistillery.Releases
without any aliases, this should be a major version-up.Some libraries which specify
{:distillery, "~> 2.0"}
likemix_erllambda
are already affected by this.The text was updated successfully, but these errors were encountered: