We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
versionScheme
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
as per https://scala-lang.org/blog/2021/02/16/preventing-version-conflicts-with-versionscheme.html and discussion at scala/sbt-scala-module#111
The text was updated successfully, but these errors were encountered:
Can we start using "early-semver" from now on, or do we have to take the past into consideration?
"early-semver"
Sorry, something went wrong.
uh, I'm not sure. off the top of my head my answer would be "from now on only".... but do you have a particular scenario or concern in mind?
I think we can go with "early-semver" then, from now on. :)
fixed by #364
No branches or pull requests
as per https://scala-lang.org/blog/2021/02/16/preventing-version-conflicts-with-versionscheme.html and discussion at scala/sbt-scala-module#111
The text was updated successfully, but these errors were encountered: