Update scala3-library to 3.3.1

[fmonniot-s-scala-steward]

About this PR

📦 Updates org.scala-lang:scala3-library from 3.2.2 to 3.3.1

📜 GitHub Release Notes - Version Diff - 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 (3.2.2).
You might want to review and update them manually.

.github/workflows/checks.yml

⚙ Adjust future updates

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

updates.ignore = [ { groupId = "org.scala-lang", artifactId = "scala3-library" } ]

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

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scala-lang", artifactId = "scala3-library" }
}]

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

[fmonniot]

Unfortunately we have to skip the 3.3.x branch. We require a bug fix that is only available in 3.4.0.

[SethTisue]

We require a bug fix that is only available in 3.4.0.

For the record, mind linking to the issue or PR in question?

[fmonniot]

Sure thing. It was discovered in #2 and fixed in scala/scala3#18092.

[SethTisue]

Hmm. I wonder why the "backport:nominated" label was removed, and if they might reconsider (or at least provide a rationale) if they knew that an important project was blocked from upgrading.

I guess it's not so bad in that your users aren't stuck on 3.2, right? It's only this repo itself that's stuck there for now?

[fmonniot]

I guess it's not so bad in that your users aren't stuck on 3.2, right? It's only this repo itself that's stuck there for now?

Yep, as long as users are ok with providing the type manually when invoking the when macro then they can upgrade to the 3.3.x serie.