-
Notifications
You must be signed in to change notification settings - Fork 396
Scala.js artifacts don’t declare a versionScheme #4513
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
Labels
enhancement
Feature request (that does not concern language semantics, see "language")
Milestone
Comments
How can we do this while still using sbt 1.2.8 ourselves? |
The simplest solution regarding the declaration of the versioning scheme would be to upgrade to sbt 1.5. If this is not possible, I guess you would have to add something like: Compile / packageBin / artifact ~= _.extra("info.versionScheme" -> "early-semver") (untested) |
sjrd
added a commit
to sjrd/scala-js
that referenced
this issue
Jun 22, 2021
sjrd
added a commit
to sjrd/scala-js
that referenced
this issue
Jun 23, 2021
sjrd
added a commit
to sjrd/scala-js
that referenced
this issue
Jun 28, 2021
sjrd
added a commit
to sjrd/scala-js
that referenced
this issue
Jul 30, 2021
sjrd
added a commit
to sjrd/scala-js
that referenced
this issue
Jul 30, 2021
…acts. We do not set the version scheme for "tools" artifacts yet, as the jury is still out on what is the best way to specify them.
sjrd
added a commit
that referenced
this issue
Jul 30, 2021
Fix #4513: Set up versionScheme for all the "library" artifacts.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The Scala.js artifacts don’t declare a versionScheme, therefore I am not sure which conclusions can be drawn from dependency resolution tools.
See e.g. scala/scala-xml#533
The text was updated successfully, but these errors were encountered: