-
Notifications
You must be signed in to change notification settings - Fork 502
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle Scala LTS and Next version updates #3328
Conversation
Scala Steward now distinguishes between Scala Next and Scala LTS. When the current Scala 3 versions is below 3.4.0 no updates to a newer Scala Next version will be created. But updates to newer Scala 3.3.x version will be created. If the current version is already a Scala Next version (3.4.x), updates to newer Scala Next versions will be created. In the future the `versionLine` property can be used to identify LTS and Next version. (scala/scala3#19986)
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #3328 +/- ##
=======================================
Coverage 91.18% 91.19%
=======================================
Files 166 166
Lines 3404 3419 +15
Branches 317 287 -30
=======================================
+ Hits 3104 3118 +14
- Misses 300 301 +1 ☔ View full report in Codecov by Sentry. |
Looks like this is not working as intended (anymore): playframework/play-json#1035 (comment), maybe #3347 broke things? |
Scala Steward now distinguishes between Scala Next and Scala LTS.
When the current Scala 3 versions is below 3.4.0 no updates to a newer Scala Next version will be created. But updates to newer Scala 3.3.x version will be created.
If the current version is already a Scala Next version (3.4.x), updates to newer Scala Next versions will be created.
In the future the
versionLine
property can be used to identify LTS and Next version. (scala/scala3#19986)fixes: #3302
followup to: #3323
I am bit unsure if I should release the changes to
default.scala-steward.conf
later, after cutting a new release and a bit of wait time, as otherwise older versions would again create pull-requests for Scala 3.4.1. But that probably has already happened in most cases.