Update scala3-library to 3.5.2

[scala-steward]

About this PR

📦 Updates org.scala-lang:scala3-library from 3.5.1 to 3.5.2

📜 GitHub Release Notes - 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!

⚙ 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-patch, semver-spec-patch, version-scheme:semver-spec, commit-count:n:2}

[coderabbitai]

📝 Walkthrough

Walkthrough

The changes in this pull request involve an update to the build.sbt file, specifically modifying the crossScalaVersions setting. The Scala version has been changed from "3.5.1" to "3.5.2", ensuring the project targets the latest version of Scala 3. No other modifications were made to the file, including library dependencies and additional settings.

Changes

File	Change Summary
build.sbt	Updated crossScalaVersions from Seq("2.12.20", "2.13.15", "3.5.1") to Seq("2.12.20", "2.13.15", "3.5.2")

Possibly related PRs

• Update scala3-library to 3.4.3 #360: Updates the crossScalaVersions in build.sbt, changing the Scala version from "3.4.3" to "3.5.0", related to version updates.
• Update scala3-library to 3.5.0 #368: Similar to the main PR, this also updates crossScalaVersions in build.sbt, changing the Scala version from "3.4.3" to "3.5.0".

🐇 In the meadow, the code does bloom,
With Scala's version, we make room.
From "3.5.1" to "3.5.2",
Hopping forward, fresh and new!
In build.sbt, the change is clear,
A brighter future, let’s all cheer! 🌼

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between a168108 and 57833ef.

⛔ Files ignored due to path filters (2)

• .github/workflows/ci.yml is excluded by !**/*.yml
• .mergify.yml is excluded by !**/*.yml

📒 Files selected for processing (1)

• build.sbt (1 hunks)

🔇 Additional comments (2)

build.sbt (2)

Line range hint 1-24: Well-maintained build configuration!

Notable observations:

• Using latest stable Slick version (3.5.2)
• Appropriate compiler options for Scala 3 compatibility (-Xsource:3)
• Test dependencies are up-to-date

---

2-2: LGTM! Safe patch version update.

The update from Scala 3.5.1 to 3.5.2 is a patch version change, which should be backward compatible. The PR is automated by scala-steward and includes links to release notes and version diff for verification.

Let's verify the compatibility of this version with the project's dependencies:

✅ Verification successful

✅ Safe to update to Scala 3.5.2

The verification confirms this is a safe update:

• Using sbt 1.10.3 which fully supports Scala 3.5.2
• All dependencies are compatible:
  • Slick 3.5.2 matches the Scala version
  • Test dependencies are all recent versions with Scala 3 support
• Build configuration is properly set up:
  • Cross-compilation settings are correct
  • Compiler options are Scala 3 compatible (-Xsource:3)
  • No Scala 3 specific flags that would need adjustment

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify if any of the dependencies have known compatibility issues with Scala 3.5.2

# Test: Check if build.properties specifies a compatible sbt version
cat project/build.properties

# Test: Look for any scala-specific compiler options or settings that might need adjustment
rg "scalacOptions|scalaVersion|crossScalaVersions" -g "*.sbt" -g "project/*.scala"

Length of output: 412

---

Script:

#!/bin/bash
# Let's verify the dependencies and their compatibility

# Check build.sbt for library dependencies
rg "^[^/].*libraryDependencies" -A 5 build.sbt

# Check for any Scala 3 specific settings or configurations
rg "scala3|dotty" -g "*.sbt" -g "project/*.scala"

# Look for any version-specific compiler flags
rg "-Xsource|-Ywarn|-Xlint|-language:" -g "*.sbt" -g "project/*.scala"

Length of output: 578

---

Script:

#!/bin/bash
# Let's try again with properly escaped patterns

# Check build.sbt for library dependencies
rg "^[^/].*libraryDependencies" -A 5 build.sbt

# Look for any version-specific compiler flags (properly escaped)
rg "\-Xsource|\-Ywarn|\-Xlint|\-language:" -g "*.sbt" -g "project/*.scala"

# Check the entire build.sbt for a complete view of the configuration
cat build.sbt

Length of output: 1659

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.