Chris Kipp

To clarify a bit, you can also reproduce this without using `sbt-scoverage`. In your example repo just remove `sbt-scoverage`, add `-coverage-out:foo` to your `scalacOptions` and run `test`. You'll get the...

Pretty much all of these need to be updated in staging: ``` - dotty.communitybuild.CommunityBuildTestC.sourcecode - dotty.communitybuild.CommunityBuildTestC.pprint - dotty.communitybuild.CommunityBuildTestC.requests - dotty.communitybuild.CommunityBuildTestC.upickle - dotty.communitybuild.CommunityBuildTestC.cask - dotty.communitybuild.CommunityBuildTestC.geny - dotty.communitybuild.CommunityBuildTestC.fansi - dotty.communitybuild.CommunityBuildTestC.oslib - dotty.communitybuild.CommunityBuildTestC.ujson...

> I believe your change is enough to change the Mill version everywhere in the CB. Note how mill bootstrap scripts read the environmental variable to obtain the version: https://github.com/dotty-staging/geny/blob/master/mill#L10...

@anatoliykmetyuk I got everything in staging updated as well since you gave your original ✅ . This should be good to merge, but just to make sure can you or...

> Related to this issue, is there any plan to update to Scala 2.13? 🤔 From my understanding of past discussions, no. Updating to 2.13 would have huge ramifications to...

For what it's worth, I understand your frustration, but this thread on sbt probably isn't the correct place to air it as it's not the fault of sbt at all....

@eed3si9n do you have any timeline on when you'd like to get 1.8.x out? I noticed that with the latest 1.7.3 even just using `addDependencyTreePlugin` globally (which I normally do)...

> Maybe get sbt 1.7.4 out fast out with a coursier version that does not pull in Scala 2.12.17 yet? Why roll back when we can move forward? Honestly the...

> @SethTisue I just tested it with another Apple M1 (Pro) and it's fine there. 😵‍💫 This sounds like it could be something in your global `~/.sbt/1.0/plugins.sbt` or something. For...

>. For reproduction clone: https://github.com/ajozwik/quill-generic > And change build.properties to 1.7.3 Locally with this repo bumping to 1.7.3 gives me no issues. Same as above, it could be something in...