⬆️ update scalatest from 3.2.8 to 3.2.18

[scala-steward]

About this PR

📦 Updates org.scalatest:scalatest from 3.2.8 to 3.2.18

📜 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.scalatest", artifactId = "scalatest" } ]

Or, add this to slow down future updates of this dependency:

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scalatest", artifactId = "scalatest" }
}]

^{labels: test-library-update, early-semver-patch, semver-spec-patch, commit-count:1}

Summary by CodeRabbit

• Chores
  • Updated ScalaTest library dependencies to enhance performance and stability.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[coderabbitai]

Walkthrough

This update focuses on a single, yet significant change: the upgrade of the ScalaTest library dependencies from version 3.2.8 to 3.2.18. This enhancement ensures compatibility with newer features and fixes, improving the overall testing framework's reliability and efficiency.

Changes

File(s)	Change Summary
build.sbt	Updated ScalaTest version from 3.2.8 to 3.2.18.

🐇✨
In the realm of code, a small hop made,
From 3.2.8 to .18, our ScalaTest upgraded.
Bugs retreat, as tests grow strong,
In this digital burrow, where code belongs.
Let's celebrate, with joy we write,
For better tests, into the night.
🌟🐰

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-tests for this file.
• 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 tests 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 from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

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

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between a536472 and e147ae5.

Files selected for processing (1)

• build.sbt (1 hunks)

Additional comments: 1

build.sbt (1)

• 30-31: The update of ScalaTest from version 3.2.8 to 3.2.18 is correctly applied. However, there's a duplicated dependency declaration for ScalaTest with different artifact IDs (%%% and %%). This might be intentional to support both Scala.js and JVM environments, but it's important to verify this setup is still required with the updated version, especially in light of the linked issue in the FIXME comment.

Please confirm that both Scala.js (%%%) and JVM (%%) versions of ScalaTest are necessary for your project's testing setup. Additionally, consider reviewing the linked issue (scalatest/scalatest#911) to determine if it has been resolved or if any action is required on your part.

[scala-steward]

Superseded by #93.