fmonniot / scala3mock

Mocking framework for Scala 3
https://francois.monniot.eu/scala3mock
Other
19 stars 1 forks source link

Update scala3-library to 3.3.1 #17

Closed fmonniot-s-scala-steward[bot] closed 7 months ago

fmonniot-s-scala-steward[bot] commented 7 months ago

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 commented 7 months ago

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

SethTisue commented 7 months ago

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 commented 7 months ago

Sure thing. It was discovered in https://github.com/fmonniot/scala3mock/pull/2 and fixed in https://github.com/lampepfl/dotty/pull/18092.

SethTisue commented 7 months ago

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 commented 7 months ago

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.