Closed SethTisue closed 4 months ago
Question, should we:
I can do 2. manually now to unblock downstream projects, but is it enough to do 1 later on?
I think we're blocked by https://github.com/scala/scala3/pull/20171
Question, should we:
drop 0.4.x and release a new milestone (I intend to address the milestone elephant in the room in the near future)
backport 0.5.x to the latest milestone
I think either of these is fine, whichever is easiest honestly.
- Try cross publishing for 0.4 and 0.5
Definitely not this.
- Try cross publishing for 0.4 and 0.5
Definitely not this.
Yep, that's what I was hoping not to do :D
I backported munit 1.0.0-M11 for 2.13, 2.12 and 3.
munit-scalacheck requires scalacheck to be released for 0.5.0
I will bump native version in the repo once that is out and next releases would be for 0.5 then.
scalacheck 1.18.0 has been published for native 0.5.
Thanks!
this will unblock a bunch of downstream libraries from also publishing for 0.5