-
Notifications
You must be signed in to change notification settings - Fork 577
Update scalacheck to 1.15.4 #291
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
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #291 +/- ##
===========================================
+ Coverage 51.78% 51.79% +0.01%
===========================================
Files 311 311
Lines 16769 16769
Branches 985 1002 +17
===========================================
+ Hits 8684 8686 +2
+ Misses 8085 8083 -2
Continue to review full report at Codecov.
|
Scalacheck 1.14 and 1.15 are officially binary-compatible yes: https://github.com/typelevel/scalacheck/releases/tag/1.15.0 |
|
Hi @felixbr, Thank you for the PR. I'm currently working on testing the upgrade internally since Twitter works in a monorepo. |
…4 in sbt Problem Scala 3 requires Scalacheck 1.15.x but the sbt builds currently uses 1.14.x Solution Upgrade Scalacheck in build.sbt to 1.15.4 to simplify Scala 3 cross-building. Result The tests use Scalacheck 1.15.4. We still use `scalatestplus scalacheck-1-14` because there is no `1-15` version available for Scalatest 3.1.x. Closes twitter/util#291 Signed-off-by: Lily He <[email protected]> JIRA Issues: CSL-11064 Differential Revision: https://phabricator.twitter.biz/D691691
…4 in sbt Problem Scala 3 requires Scalacheck 1.15.x but the sbt builds currently uses 1.14.x Solution Upgrade Scalacheck in build.sbt to 1.15.4 to simplify Scala 3 cross-building. Result The tests use Scalacheck 1.15.4. We still use `scalatestplus scalacheck-1-14` because there is no `1-15` version available for Scalatest 3.1.x. Closes twitter/util#291 Signed-off-by: Lily He <[email protected]> JIRA Issues: CSL-11064 Differential Revision: https://phabricator.twitter.biz/D691691
…4 in sbt Problem Scala 3 requires Scalacheck 1.15.x but the sbt builds currently uses 1.14.x Solution Upgrade Scalacheck in build.sbt to 1.15.4 to simplify Scala 3 cross-building. Result The tests use Scalacheck 1.15.4. We still use `scalatestplus scalacheck-1-14` because there is no `1-15` version available for Scalatest 3.1.x. Closes twitter/util#291 Signed-off-by: Lily He <[email protected]> JIRA Issues: CSL-11064 Differential Revision: https://phabricator.twitter.biz/D691691
…4 in sbt Problem Scala 3 requires Scalacheck 1.15.x but the sbt builds currently uses 1.14.x Solution Upgrade Scalacheck in build.sbt to 1.15.4 to simplify Scala 3 cross-building. Result The tests use Scalacheck 1.15.4. We still use `scalatestplus scalacheck-1-14` because there is no `1-15` version available for Scalatest 3.1.x. Closes twitter/util#291 Signed-off-by: Lily He <[email protected]> JIRA Issues: CSL-11064 Differential Revision: https://phabricator.twitter.biz/D691691
|
Thanks again for the PR. This was merged yesterday. I bumped the Scalacheck version for the other libraries as well. |
Note: This is split out from the big WIP PR #290 and can be done separately as preparation for Scala 3.
Problem
Scala 3 requires Scalacheck 1.15.x but the build currently uses 1.14.x
Solution
Upgrading Scalacheck should be fairly simple as I've yet to see any binary compatibility issues between 1.14.x and 1.15.x.
If we can use the newer version across all Scala versions it will simplify Scala 3 cross-building (otherwise we'd have to use different versions which can be finicky).
Result
The tests use Scalacheck 1.15.4.
We still use
scalatestplus scalacheck-1-14because there is no1-15version available for Scalatest 3.1.x but in my experience there are no binary compatibility issues, so it's worth a try. Since this only affects tests the small risk of a crash is acceptable (and problems should be found in CI).Cheers
~ Felix