Third party dependency updates

[flow-tech]

About this PR

Updates:

• 📦 org.scoverage:sbt-scoverage from 2.4.0 to 2.4.1
  • 📜 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 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!

🔍 Files still referring to the old version numbers

The following files still refer to the old version numbers.
You might want to review and update them manually.

src/test/scala/io/flow/util/VersionParserSpec.scala

⚙ Adjust future updates

Add these to your .scala-steward.conf file to ignore future updates of these dependencies:

updates.ignore = [
  { groupId = "org.scoverage", artifactId = "sbt-scoverage" }
]

Or, add these to slow down future updates of these dependencies:

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

^{labels: scala-steward}

Summary by CodeRabbit

• Chores
  • Updated code coverage tool dependency to the latest patch version.

[coderabbitai]

📝 Walkthrough

Walkthrough

Updates the scoverage sbt plugin dependency version from 2.4.0 to 2.4.1 in the build configuration file. This is a patch-level version bump for the artifact org.scoverage:sbt-scoverage.

Changes

Cohort / File(s)	Change Summary
Build Configuration project/plugins.sbt	Version bump: org.scoverage % sbt-scoverage % 2.4.0 → 2.4.1

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Third party dependency updates #257: Prior scoverage plugin version upgrade (2.3.1→2.4.0) affecting the same project/plugins.sbt file.

Suggested reviewers

• jackl
• gheine

Pre-merge checks

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Third party dependency updates' is generic and vague, using non-descriptive terms that don't convey the specific change.	Provide a more specific title like 'Bump org.scoverage:sbt-scoverage to 2.4.1' to clearly identify the actual dependency being updated.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a4fe2a0 and 4ed038b.

📒 Files selected for processing (1)

• project/plugins.sbt (1 hunks)

🔇 Additional comments (1)

project/plugins.sbt (1)

9-9: No changes needed; test file reference is generic and unrelated to plugin version.

The version bump to 2.4.1 is correct. The reference to "2.4.0" in src/test/scala/io/flow/util/VersionParserSpec.scala:146 is generic test data for the VersionParser utility (specifically within the "webjars-play version numbers" test case), not a reference to the sbt-scoverage plugin version. This test data should not be updated.

No security advisories exist for sbt-scoverage 2.4.1.

Likely an incorrect or invalid review comment.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[flow-tech]

Click here for code coverage report: https://jenkins.flo.pub/job/flowcommerce/job/lib-util/job/PR-259/3/scoverage-report/