-
Notifications
You must be signed in to change notification settings - Fork 333
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
publish for Scala 2.13.0-RC1 #1567
Comments
Hi @SethTisue , Thanks for informing, no longer depends on ScalaCheck but I think still depend on scala-xml. I'll try it out today and see if there's any stopper from publishing. |
@SethTisue Actually 3.0.x still depends on ScalaCheck, but the main blocker currently is scala-xml: Will wait a little bit for it. Thanks. |
scala-xml 1.2.0 is on Maven Central |
ScalaCheck 1.14.0 is now fully published |
@SethTisue I released 3.0.8-RC2 that supports 2.13.0-RC1 jvm and scala-js 0.6 build, will build for scala-js 1.0.0-M7 once scalacheck supports it. |
artifacts have appeared at https://repo1.maven.org/maven2/org/scalatest/scalatest_2.13.0-RC1/ 👍 |
@SethTisue I'll work on release for 3.1.x next, by the way, may I know what's the best channel to report bug/problem for the RC1? I remember there's a JIRA but not sure if it applies for RC release too. Thanks! |
@cheeseng https://github.com/scala/bug is the place |
@SethTisue Thanks for the link! Is there by any chance for scala-parser-combinators will be released for 2.13.0-RC1? It won't block the quick release as we only depend on it in tests in 3.1.x branch, but will be nice to be able to run the tests to know which are failing. Thanks! |
it is, version 1.1.2. but be careful on Scala 2.11; see scala/scala-parser-combinators#197 |
ScalaTest 3.0.8-RC2 has been published for Scala 2.13.0-RC1 @cheeseng is this ticket still open on purpose, is there something left to do here, or should we close it? |
RC1 is on Maven Central
does publishing still depend on ScalaCheck? @rickynils has been notified and a prompt ScalaCheck release is expected (ticket: typelevel/scalacheck#464)
The text was updated successfully, but these errors were encountered: