Update utest to 0.8.5

[scala-steward]

About this PR

📦 Updates com.lihaoyi:utest from 0.8.4 to 0.8.5

📜 GitHub Release Notes - Version Diff

Usage

✅ Please merge!

I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.

If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.

Configure Scala Steward for your repository with a .scala-steward.conf file.

Have a fantastic day writing Scala!

🔍 Files still referring to the old version number

The following files still refer to the old version number (0.8.4).
You might want to review and update them manually.

integration/ide/gen-idea/resources/hello-idea/idea/mill_modules/helloideajs.test.iml
readme.adoc
scalalib/test/src/mill/scalalib/ScalaMultiModuleClasspathsTests.scala

⚙ Adjust future updates

Add this to your .scala-steward.conf file to ignore future updates of this dependency:

updates.ignore = [ { groupId = "com.lihaoyi", artifactId = "utest" } ]

Or, add this to slow down future updates of this dependency:

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.lihaoyi", artifactId = "utest" }
}]

^{labels: library-update, early-semver-minor, semver-spec-patch, old-version-remains, commit-count:1}

[lefou]

I think the last failing CI test (something "mockito") is unrelated to this bump.

[lihaoyi]

yeah that mockito test seems to have gotten super flaky suddenly, not sure why

[lefou]

@lihaoyi How do you merge nowadays? I don't find my co-authorship in the final commit of this PR. Although Github should generate it properly when you squash-merge via the UI buttons. It's not that problematic in this case, but in general, if we squash and erase all traces of the work that lead to a change, we should at least use the appropriate git capabilities to attribute authorship.

[lihaoyi]

@lefou I've just been using the squash-and-merge button on github.

[lefou]

Maybe, you manually removed the lengthy commit message body that Scala Steward generated (as I do it) and overlooked that there was a Co-authored-by: line at the end?

Since I'm missing myself as author also in some other commits in this repo, I'd like to remind everyone, that we should take authorship not lightly! Beside being just fair, especially in Open Source projects based on voluntary contributions, I often use this info later, when digging something up in history. It can become frustrating if you can't find a change you made, just because all traces that you made that change are gone.

[lihaoyi]

Oh yes I've been removing the long commit message body for these scala steward commits. I can try to leave the co-authored-by suffix next time