Update scalatest to 3.2.18

[scala-steward-asf]

About this PR

📦 Updates org.scalatest:scalatest from 3.2.17 to 3.2.18

📜 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!

⚙ Adjust future updates

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

updates.ignore = [ { groupId = "org.scalatest", artifactId = "scalatest" } ]

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

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scalatest", artifactId = "scalatest" }
}]

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

[mdedetrich]

@pjfanning Isn't the better way to solve this problem just to pin the dependencies with a .scala-steward.conf or am I missing something?

[pjfanning]

@mdedetrich you are suggesting that we skip scalatest 3.2.18 and stick with 3.2.17? It is a bit annoying of scalatest to upgrade to mockito and testng versions that don't support Java 8 in what in semver terms is a patch release.

[mdedetrich]

I just realized that this repo is already on 1.1.x so you can ignore my previous comment. So yes we should figure out the core underlying issue.

[raboof]

LGTM, though it is unfortunate we must use scalatest modules that are built for a different version of scalatest. Since these are only test dependencies that seems fine for now though.

Filed #1118 so we're reminded to fix this again once we move to requiring later Java versions for the build.