Flow dependency updates

[flow-tech]

About this PR

Updates:

• 📦 io.flow:lib-test-utils-play29 from 0.2.85 to 0.2.86

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!

⚙ Adjust future updates

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

updates.ignore = [
  { groupId = "io.flow", artifactId = "lib-test-utils-play29" }
]

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

dependencyOverrides = [
  {
    pullRequests = { frequency = "30 days" },
    dependency = { groupId = "io.flow", artifactId = "lib-test-utils-play29" }
  }
]

^{labels: scala-steward}

Summary by CodeRabbit

• Chores
  • Updated test dependencies to latest versions.

[coderabbitai]

📝 Walkthrough

Walkthrough

Updated the test dependency lib-test-utils-play29 from version 0.2.85 to 0.2.86 in build.sbt. This is a patch-level version bump with no changes to build logic or functionality.

Changes

Cohort / File(s)	Summary
Dependency version bump build.sbt	Updated lib-test-utils-play29 test dependency from 0.2.85 to 0.2.86

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Verify the version number matches the intended release
• Confirm lib-test-utils-play29 0.2.86 is available in the configured repository

Possibly related PRs

• Flow dependency updates #387: Consecutive version bump PR for the same dependency (0.2.84→0.2.85 predecessor)
• Flow dependency updates #386: Updates the same lib-test-utils-play29 dependency in build.sbt
• Flow dependency updates #382: Modifies the same test-scoped dependency in build.sbt

Suggested labels

auto-merge

Pre-merge checks

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Flow dependency updates' is vague and overly broad, using a generic term that does not convey the specific dependency being updated or the concrete nature of the change.	Make the title more specific by identifying the actual dependency updated, such as 'Update lib-test-utils-play29 to 0.2.86' or 'Bump lib-test-utils-play29 dependency version'.

✅ 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 a56f7aa and 6902473.

📒 Files selected for processing (1)

• build.sbt (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Jenkins

🔇 Additional comments (1)

build.sbt (1)

36-36: LGTM! Test dependency patch update.

This is a straightforward patch-level version bump (0.2.85 → 0.2.86) for a test-scoped dependency. Since this is an internal library from the same organization and limited to test scope, the change poses minimal risk.

---

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