update SBT to 2.0.6

[mr-git]

No description provided.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[coderabbitai]

Warning

Review limit reached

@mr-git, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 21 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: b1a7e261-ec38-4e02-9f88-ccfd10fdb203

📥 Commits

Reviewing files that changed from the base of the PR and between 1a1f708 and 7e273a2.

📒 Files selected for processing (2)

• build.sbt
• project/build.properties

---

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

[coveralls]

Coverage Report for CI Build 31417397213

Coverage increased (+0.5%) to 82.598%

Details

• Coverage increased (+0.5%) from the base build.
• Patch coverage: No coverable lines changed in this PR.
• 297 coverage regressions across 25 files.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

297 previously-covered lines in 25 files lost coverage.

Top 10 Files by Coverage Loss	Lines Losing Coverage	Coverage
com/evolutiongaming/skafka/consumer/Consumer.scala	82	83.29%
com/evolutiongaming/skafka/producer/ProducerMetricsOf.scala	42	66.93%
com/evolutiongaming/skafka/producer/ProducerMetrics.scala	38	44.33%
com/evolutiongaming/skafka/consumer/ConsumerMetrics.scala	33	42.66%
com/evolutiongaming/skafka/consumer/ConsumerMetricsOf.scala	20	4.44%
com/evolutiongaming/skafka/metrics/KafkaMetricsCollector.scala	16	6.16%
com/evolutiongaming/skafka/Converters.scala	15	82.48%
com/evolutiongaming/skafka/KafkaHealthCheck.scala	12	77.31%
com/evolutiongaming/skafka/metrics/KafkaMetricsRegistry.scala	11	27.27%
com/evolutiongaming/skafka/producer/Producer.scala	5	73.61%

---

Coverage Stats

Relevant Lines:	2835
Covered Lines:	2412
Line Coverage:	85.08%
Relevant Branches:	544
Covered Branches:	379
Branch Coverage:	69.67%
Branches in Coverage %:	Yes
Coverage Strength:	1.35 hits per line

---

💛 - Coveralls