Update scalafmt-core to 3.1.1

[scala-steward]

Updates org.scalameta:scalafmt-core from 3.1.0 to 3.1.1.
GitHub Release Notes - Version Diff

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 (3.1.0).
You might want to review and update them manually.

.github/workflows/ci.yml
README.md
build.sbt
core/shared/src/main/scala/fs2/Stream.scala
core/shared/src/main/scala/fs2/text.scala
io/js/yarn.lock
io/jvm/src/main/scala/fs2/io/file/DeprecatedFilesApi.scala
node/js/yarn.lock

Ignore future updates

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

updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalafmt-core" } ]

labels: library-update, early-semver-patch, semver-spec-patch, old-version-remains

[mpilquist]

Scalafix tests are failing due to the reformat. We could either exclude scalafix from Scalafmt or we could figure out how to fix those tests.

[vasilmkd]

@mpilquist In Cats Effect we're facing the same issue. I usually revert the formatting changes to the output files manually. I don't have a better fix unfortunately.

Here's an example PR.

typelevel/cats-effect#2538

[mpilquist]

Oh huh, is this because of the way @scala-steward runs the Scalafmt on all subprojects or something? Whereas our fmtCheck/fmt alias only runs it on certain subprojects?

[fthomas]

Scala Steward runs the scalafmt binary in the root directory for reformatting instead of using the sbt-scalafmt plugin. Excluding the scalafix/ directory in .scalafmt.conf sounds like a sensible solution to me.

[mpilquist]

Thanks Frank! I hadn't gotten to the point of figuring out how to exclude. I like the .scalafmt.conf option.

[vasilmkd]

@fthomas We have a .scalafmt.conf inside scalafix/ in Cats Effect. That seems ignored? Do we get anything from having that file or can we remove it in favor of an ignore configuration in the root config file?

Here are the files in question:
https://github.com/typelevel/cats-effect/blob/c26a1ea4b1d113abb7c9e6c9c7f72e4dd86fbcb5/scalafix/.scalafmt.conf
https://github.com/typelevel/cats-effect/blob/c26a1ea4b1d113abb7c9e6c9c7f72e4dd86fbcb5/.scalafmt.conf

Thanks.

[fthomas]

@vasilmkd

We have a .scalafmt.conf inside scalafix/ in Cats Effect. That seems ignored?

Yes, I think so. It probably only reads one config per run. So if it is executed in the root dir, it will only read the .scalafmt.conf there.

I would keep the scalafix/.scalafmt.conf in place and just add project.excludeFilters = [ "scalafix/*" ] (or is it excludePaths?) to the root configuration.