Skip to content
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

Merged
merged 4 commits into from
Apr 26, 2024
Merged

Handle Scala LTS and Next version updates #3328

merged 4 commits into from
Apr 26, 2024

Conversation

mzuehlke
Copy link
Member

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.

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)
@mzuehlke mzuehlke changed the title Handle Scala LTS and Next version update Handle Scala LTS and Next version updates Mar 31, 2024
Copy link

codecov bot commented Mar 31, 2024

Codecov Report

Attention: Patch coverage is 94.11765% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 91.19%. Comparing base (2e246d0) to head (5dbe442).
Report is 22 commits behind head on main.

❗ Current head 5dbe442 differs from pull request most recent head 85225b2. Consider uploading reports for the commit 85225b2 to get more accurate results

Files Patch % Lines
...scala/org/scalasteward/core/update/FilterAlg.scala 92.30% 1 Missing ⚠️
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.
📢 Have feedback on the report? Share it here.

@mzuehlke mzuehlke merged commit 996af6a into main Apr 26, 2024
8 checks passed
@mzuehlke mzuehlke deleted the scala-lts-filter branch April 26, 2024 15:05
@mzuehlke mzuehlke added this to the 0.30.0 milestone Apr 26, 2024
@mzuehlke mzuehlke added the enhancement New feature or request label Apr 26, 2024
@mkurz
Copy link
Contributor

mkurz commented May 8, 2024

Looks like this is not working as intended (anymore): playframework/play-json#1035 (comment), maybe #3347 broke things?

@mzuehlke
Copy link
Member Author

mzuehlke commented May 8, 2024

@mkurz
I found a bug and created a PR that will prevent such PRs in the future: #3354

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Avoid pushing scala updates for non LTS versions
2 participants