-
-
Notifications
You must be signed in to change notification settings - Fork 215
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
Compatibility error after updating from 4.19.0 to 4.19.1 #1130
Comments
we also have issue when update specs2-core to 4.19.1 in scalachess
|
Do we have changelog or commits diff between two versions somewhere? |
This is weird, the only code change that has gone in is here: https://github.com/etorreborre/specs2/pull/1128/files. It is just adding one object, so I don't think that is a problem. The other change which could have an impact on compatibility is this one: b60527a. @amumurst maybe you can try upgrading your scala version here: https://github.com/amumurst/highgarden/blob/master/build.sbt#L28. @lenguyenthanh on the other hand you don't seem to have the same issue since you are already on Scala 3.2.1: https://github.com/lichess-org/scalachess/blob/master/build.sbt#L35. Is your error coming from a full recompilation? |
yes, I got this after full recompilation. |
I checked and updating scala version to 3.2.1 does not help my project either. Done full recompilation (even deleting all target folders). Also tried both jdk 8, 13 and 17 just for good measure, no change. |
Ok, I think I understand the situation. I got confused with my own set-up for Scala2 / Scala3 and the 4.x / 5.x series. The version I have now published 4.19.2 which is from the |
@amumurst I tested it on your project and all the tests pass. |
I tried updating specs2 in my example repo and found that migrating to 4.19.1 did not work automatically.
Project uses
specs2
andcats-effect-testing-specs2
(scala 3), link to project https://github.com/amumurst/highgardencats-effect-testing-specs2 depends on 4.17.0 (from inspecting evictions in sbt)
org.specs2:specs2-core_3:4.17.0 (evicted by 4.19.1)]
. So evicting from 4.17.0=>4.19.0 is ok, not to 4.19.1. Pr from steward to update in CE testing (typelevel/cats-effect-testing#413)Running
testOnly no.amumurst.http.CarEndpointsSpec
on 4.19.0 completes successfully.Changing to version 4.19.1 spits out this instead:
The text was updated successfully, but these errors were encountered: