Update scala3-library to 3.5.0

[scala-steward]

About this PR

📦 Updates org.scala-lang:scala3-library from 3.4.3 to 3.5.0

📜 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!

⚙ 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, commit-count:n:2}

[coderabbitai]

Walkthrough

Walkthrough

The updates across the project involve upgrading the Scala version from 3.4.3 to 3.5.0 in multiple configuration files. This includes changes in the CI workflow, Mergify configuration, and build settings, ensuring the project aligns with the latest Scala features and improvements. The modifications encompass adjustments to job names and environment specifications to reflect the new version.

Changes

File	Change Summary
.github/workflows/ci.yml	Updated Scala version from 3.4.3 to 3.5.0 in job configurations and renamed download steps accordingly.
.mergify.yml	Updated build and test environment version from 3.4.3 to 3.5.0 for the Ubuntu environment.
build.sbt	Changed crossScalaVersions from "3.4.3" to "3.5.0".

Poem

🐰 In the garden of code, we hop with glee,
Upgrading Scala, so fresh and so free!
From 3.4.3 to 3.5, we dance and we play,
With features anew, we brighten the day!
So let’s celebrate this version so bright,
Hopping through code, what a joyful sight! 🌼

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 89fab28 and 4e45db4.

Files selected for processing (3)

• .github/workflows/ci.yml (3 hunks)
• .mergify.yml (1 hunks)
• build.sbt (1 hunks)

Files skipped from review due to trivial changes (1)

• .mergify.yml

Additional comments not posted (2)

build.sbt (1)

2-2: Scala version update approved.

The Scala version has been updated from 3.4.3 to 3.5.0 in the crossScalaVersions setting. This aligns with the PR objectives and ensures compatibility with the latest Scala features and improvements.

.github/workflows/ci.yml (1)

26-26: CI configuration update approved.

The Scala version has been updated from 3.4.3 to 3.5.0 in the CI workflow configuration. This ensures that the CI pipeline is aligned with the latest Scala version, which may include performance improvements, new features, or bug fixes.

Also applies to: 68-68, 105-108, 110-110