Closed tgodzik closed 4 months ago
This is blocked by the issue in LTS
Just thinking loud, would we loose anything if we move munit to 3.3.3 and uncomment the failing test ? The people who are on Scala LTS and use munit would still not get the right error message. We just have to remember to enable the tests once the fix landed in LTS
At minimum, munit needs to move to 3.3.x to consume the scalacheck artifacts.
Maybe yeah. I will do that in this pr
I will go ahead and merge this, then release next and hopefully last milestone
Fixes https://github.com/scalameta/munit/issues/760