-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
Dependencies inconsistent with scala-output-version #23
Comments
Yikes. I should probably just downgrade to 3.0.2. |
Or, possibly just go to 3.1 :) see discussion in: tl;dr is that we should definitely pin to a Scala 3 version, but there seems little good reason to make it 3.0. |
Maybe you're right. I noticed 3.1.2 having type inference issues, not happening in 3.1.0, which is why I've had to fill some obvious type params; possibly a bug I need to minimize and report, which made me want to downgrade to 3.0 for the output. |
Speaking of the Scala bug: scala/scala3#15160 I'm going to make another release soon, bumping the Scala compiler to 3.1.1. |
I published https://github.com/monix/newtypes/releases/tag/v0.2.3 |
Unfortunately setting the
-scala-output-version
flag is not sufficient. Currently newtypes is published with a dependency on the Scala 3.1.2 standard lib, which makes it difficult to use from a Scala 3.0 project :)https://repo1.maven.org/maven2/io/monix/newtypes-core_3/0.2.2/newtypes-core_3-0.2.2.pom
Configuring this is complex enough that sbt will be getting special support for it in 1.7.0:
https://github.com/sbt/sbt/releases/tag/v1.7.0-M2
The text was updated successfully, but these errors were encountered: