-
Notifications
You must be signed in to change notification settings - Fork 90
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 version 0.10? #201
Comments
I fixed the README in 4627fe0 to go back to recommending 0.9.7 @LeifW @sergiorussia are there particular changes on the master branch that you're interested in seeing released? or are you fine with continuing to use 0.9.7, and you only opened the issue because of what the readme said? @retronym might it be time to roll 0.10? |
This comment has been minimized.
This comment has been minimized.
@SethTisue i think ppl are eager to get latest stability fixes and performance improvements anyways. can't say anything regarding new commits in master (there are a lot of them) but as for me and my colleagues we hope to see #89 some day closed - it's the most inconvenient thing ever about scala-async 😞 (Python's 3.5+ async-await feels so natural...) |
@retronym shall I roll 0.10 with whatever's currently on master? |
Just released 0.10.0 for Scala 2.12 and 2.13.0-M5. |
RC1, surely :-) |
@retronym 0.10.0 depends on scala 2.12.8 - is that a minimum required version for java8? just found that simply raising scala-async version automatically bumped resulting scalaVersion from explicit 2.12.7 to implicit 2.12.8 |
@sergiorussia I'm not able to reproduce that:
are you doing something different? |
@SethTisue i found the problemactic setting:
gives
|
That's the version the README says to use, but apparently it's not on Maven central.
The text was updated successfully, but these errors were encountered: