Flow dependency updates

[flow-tech]

About this PR

Updates:

• 📦 io.flow:lib-test-utils-play29 from 0.2.69 to 0.2.70

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
  • Bumped a test-only dependency to the latest patch version to align with ecosystem updates and reduce maintenance risk. Build configuration updated as part of routine upkeep.
• Tests
  • Improves test suite stability and compatibility. No impact on production code, performance, or user-facing behavior.

[Copilot]

Copilot wasn't able to review any files in this pull request.

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Updated a test-scoped dependency in build.sbt: io.flow %% lib-test-utils-play29 was bumped from version 0.2.69 to 0.2.70. No other build or source changes are included.

Changes

Cohort / File(s)	Summary of Changes
Build configuration build.sbt	Bump io.flow %% lib-test-utils-play29 from 0.2.69 to 0.2.70 in Test scope

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Pre-merge checks (3 passed)

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title succinctly indicates that a Flow dependency is being updated and relates directly to the change, though it is somewhat broad and could specify the exact artifact and version for added clarity.
Description Check	✅ Passed	The description clearly details the dependency change, naming the exact artifact and version bump along with relevant usage instructions, and is directly related to the changeset.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch update/flow

---

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

build.sbt (1)

40-40: Remove deprecated Bintray resolver

dl.bintray.com has been offline for years; keeping it slows resolution and can fail builds. Recommend dropping it.

Apply:

-    resolvers += "scalaz-bintray" at "https://dl.bintray.com/scalaz/releases",

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a690535 and 13f73d6.

📒 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: Approve test-only dep bump; manual eviction check required

No runtime impact expected, scoped to Test. sbt isn’t available in this environment—run

sbt -no-colors "update; evicted; Test / test"

locally to confirm no evictions or regressions.

[flow-tech]

Click here for code coverage report: https://jenkins.flo.pub/job/flowcommerce/job/lib-postgresql/job/PR-371/1/scoverage-report/