recent typelevel library updates#52
Conversation
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📝 WalkthroughWalkthroughUpdates to build configuration and dependencies (Scala, sbt plugins, library versions) plus removal of trailing Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Fix all issues with AI agents
In `@build.sbt`:
- Around line 4-5: Update CI and local verification to build and run the full
test suite against both scala213 ("scala213") and scala3 ("scala3") declared in
build.sbt; search the codebase for case classes that override productPrefix or
hashCode (they can behave differently under 2.13.17) and adapt those overrides
to not rely on productPrefix, or remove custom hashCode logic, and add targeted
tests. Audit uses of scala.util.Using (search for Using.apply/manager) for code
that assumes suppressed-exception ordering and explicitly catch/control
ControlThrowable cases or avoid relying on suppression ordering by manually
adding suppressed exceptions. For Scala 3, fix interpolator usages that
implicitly call toString (replace with explicit .show/.toString or safer
formatting) and resolve implicit defaults that shadow given declarations (rename
or make givens explicit) to avoid new warnings (or adjust compiler flags in
build.sbt/ci if necessary), then re-run tests on both versions and fix any
failures.
In `@project/Versions.scala`:
- Around line 3-7: The doobie version in Versions.scala is set to a release
candidate (val doobie = "1.0.0-RC11"); mark this as an RC in the PR notes and do
not treat it as a final upgrade until validated, then run integration tests that
exercise Postgres JSON/JSONB array mappings and Scala 3 enum-derived Read/Write
instances (or any codepaths using those features) to confirm compatibility
before merging; if tests fail or you rely on those features, either pin back to
the previous stable doobie version or add targeted test coverage and a follow-up
task to revisit doobie after a final release.
- Line 23: The project sets val zioInteropCats = "23.1.0.13" but that release
requires ZIO 2.1.23 while the project currently uses ZIO 2.1.19; update
Versions.scala to fix the mismatch by either (A) bumping the ZIO version
constant (val zioVersion or whatever ZIO version symbol is defined) to "2.1.23"
and re-run the build/tests, or (B) downgrade val zioInteropCats to a prior
interop-cats release that is compatible with ZIO 2.1.19; pick one approach,
change the corresponding val in Versions.scala, and run the CI/build to verify
compatibility (also verify cats-effect compatibility as noted).
| val scala213 = "2.13.17" | ||
| val scala3 = "3.3.7" |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
cd . && find . -name "build.sbt" -type f -exec head -50 {} + | head -100Repository: kaizen-solutions/trace4cats-zio-extras
Length of output: 1878
🌐 Web query:
Scala 2.13.17 release notes breaking changes
💡 Result:
Scala 2.13.17 (released October 6, 2025) lists two breaking changes in its release notes:
-
Case class
hashCodechanges whenproductPrefixis overridden- Change: “Mix in the
productPrefixhash statically in case classhashCode.” - Impact: the synthetic
hashCodeof a case class no longer callsproductPrefix, so the hash code changes for case classes that overrideproductPrefix. [1]
- Change: “Mix in the
-
scala.util.Usingsuppressed-exception ordering changed- Change: “Improve
scala.util.Usingsuppression order (NonFatalsuppressesControlThrowable).” - Impact: when multiple exceptions occur, the ordering of which exception is rethrown vs. attached as suppressed can differ from previous versions. [1]
- Change: “Improve
Sources: Scala 2.13.17 GitHub release notes [1]; Scala-lang announcement (points to GitHub notes) [2].
🌐 Web query:
Scala 3.3.7 release notes breaking changes compatibility
💡 Result:
Scala 3.3.7 (LTS) was released on October 13, 2025. It is a patch release, and the Scala team states the backports were validated to not break binary or source compatibility (tested across 1500+ projects in the Scala 3 Open Community Build). [1][3]
Breaking changes / compatibility notes
- No intentional breaking changes (binary or source) are expected vs earlier 3.3.x releases. [1]
- Potentially “compatibility-affecting in practice” items are mostly:
- New/adjusted warnings (could fail builds that use
-Werror/ strict warning policies), e.g. warning when an interpolator usestoString, and warning when an implicit default shadows agiven. [1] - REPL command change:
:jarwas implemented and:requirewas deprecated (so existing REPL workflows/scripts using:requiremay need updating). [1]
- New/adjusted warnings (could fail builds that use
Notable changes called out in the announcement
- Warn if interpolator uses
toString[1] - Fix: unblock Scala 3 on Android [1]
- REPL: implement
:jar(deprecate:require) [1] -Wunused/unused-import checking improvement (import qualifier/prefix matching) [1]- REPL: flag to quit after evaluating init script [1]
- Warn if implicit default shadows
given[1] - Coverage behavior made closer to Scala 2 [1]
Primary references (release notes/announcement): Scala 3.3.7 announcement and the scala3 GitHub releases page. [1][2]
Verify codebase compatibility with Scala 2.13.17 and 3.3.7 breaking changes.
Scala 2.13.17 introduces two breaking changes:
- Case class
hashCodenow excludesproductPrefix(affects only case classes that overrideproductPrefix) scala.util.Usingsuppressed-exception ordering changed (NonFatalnow suppressesControlThrowable)
Scala 3.3.7 (patch/LTS) has no breaking changes vs 3.3.x, but adds new warnings for interpolators using toString and implicit defaults shadowing given declarations—these may fail builds with -Werror.
Confirm your test suite passes against both versions and review code for these specific patterns.
🤖 Prompt for AI Agents
In `@build.sbt` around lines 4 - 5, Update CI and local verification to build and
run the full test suite against both scala213 ("scala213") and scala3 ("scala3")
declared in build.sbt; search the codebase for case classes that override
productPrefix or hashCode (they can behave differently under 2.13.17) and adapt
those overrides to not rely on productPrefix, or remove custom hashCode logic,
and add targeted tests. Audit uses of scala.util.Using (search for
Using.apply/manager) for code that assumes suppressed-exception ordering and
explicitly catch/control ControlThrowable cases or avoid relying on suppression
ordering by manually adding suppressed exceptions. For Scala 3, fix interpolator
usages that implicitly call toString (replace with explicit .show/.toString or
safer formatting) and resolve implicit defaults that shadow given declarations
(rename or make givens explicit) to avoid new warnings (or adjust compiler flags
in build.sbt/ci if necessary), then re-run tests on both versions and fix any
failures.
| val catsEffect = "3.6.3" | ||
| val doobie = "1.0.0-RC11" | ||
| val embeddedPostgres = "2.1.0" | ||
| val fs2 = "3.12.0" | ||
| val fs2Kafka = "3.8.0" | ||
| val fs2 = "3.12.2" | ||
| val fs2Kafka = "3.9.1" |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
cats-effect 3.6.3 release notes breaking changes compatibility
💡 Result:
Cats Effect 3.6.3 — release notes / breaking changes / compatibility
- Release notes (what changed): 3.6.3 is primarily a bugfix release. It fixes a bug introduced in 3.6.2 that could “poison” the thread pool and cause severe performance degradation; upgrading from 3.6.2 to 3.6.3 is strongly recommended. The only listed change is a spinlock fix (PR
#4449). [1] - Breaking changes: The 3.6.3 release notes explicitly state it is fully binary compatible with every Cats Effect 3.x release and fully source-compatible within the 3.6.x line—so no intentional breaking changes are called out for 3.6.3. [1]
- Compatibility notes:
- Scala Native: Cats Effect 3.6.x targets Scala Native 0.4.x and therefore does not support native multithreading in this series (planned for a later minor line). [1]
- Supported platforms (3.6.x artifacts): Scala.js 1.x and Scala Native 0.4. [2]
Sources:
[1] Cats Effect GitHub Releases — v3.6.3 notes
[2] Scala Index — cats-effect 3.6.x artifact metadata (Scala.js/Scala Native versions)
🌐 Web query:
doobie 1.0.0-RC11 release notes features stability
💡 Result:
doobie 1.0.0-RC11 (released Nov 8, 2025) — release notes / features / stability
Notable new features / changes
- Postgres: adds
Array[Json]instances (improves mapping support for Postgres JSON arrays). [1] - Scala 3: adds enum derivation support (plus documentation for it). [1]
Dependency / maintenance updates (highlights)
- Updates cats-effect / cats-effect-testkit to 3.6.3. [1]
- Updates HikariCP to 7.0.2. [1]
- Updates PostgreSQL JDBC driver to 42.7.8. [1]
- Updates fs2 to 3.12.2, munit to 1.2.0, circe to 0.14.15, mysql-connector-j to 9.4.0, scala-collection-compat to 2.14.0. [1]
- H2 update to address a security vulnerability. [1]
Stability take
- RC11 appears to be a small, targeted RC (two user-facing feature items) plus dependency/security updates, which generally suggests low behavioral churn relative to earlier RCs—but it is still a release candidate, so you should run your integration test suite, especially around:
- Postgres JSON/JSONB array mappings
- Scala 3 enum-derived
Read/Write/Get/Putusage - Connection pooling behavior if you rely on HikariCP defaults [1]
Sources: doobie GitHub release notes for v1.0.0-RC11 [1]; Scala Index release metadata for 1.0.0-RC11 artifacts [2].
[1] (github.com)
[2] (index.scala-lang.org)
Citations:
- 1: https://github.com/tpolecat/doobie/releases
- 2: https://index.scala-lang.org/typelevel/doobie/artifacts/doobie-core/1.0.0-RC11?utm_source=openai
🌐 Web query:
fs2 3.12.2 release notes breaking changes
💡 Result:
FS2 v3.12.2 (released Sep 4, 2025) is a bugfix/security release and its release notes do not list any breaking changes. [1], [2]
What changed in 3.12.2:
- Includes remediation for security advisory GHSA-rrw2-px9j-qffj (TLS on JVM: upgrade recommended to 3.12.1+). [1], [3]
- Bugfix: Backport
#3591(fix related to issue#3590; released via PR #3603). [1], [4]
Bottom line: No API/behavior-breaking changes are called out in the official v3.12.2 release notes—just a targeted backported fix plus the security remediation note. [1]
Sources
[1] FS2 GitHub Releases – v3.12.2 notes: (github.com)
[2] Scala Index – fs2-core 3.12.2 (release date): (index.scala-lang.org)
[3] GHSA-rrw2-px9j-qffj advisory (typelevel/fs2): (github.com)
[4] PR #3591 (fix) / backport referenced by release notes: (github.com)
Citations:
- 1: https://github.com/typelevel/fs2/releases
- 2: https://index.scala-lang.org/typelevel/fs2/artifacts/fs2-core/3.12.2?utm_source=openai
- 3: GHSA-rrw2-px9j-qffj
- 4: Fix for https://github.com/typelevel/fs2/issues/3590 typelevel/fs2#3591
🌐 Web query:
fs2-kafka 3.9.1 release notes compatibility
💡 Result:
fs2-kafka 3.9.1 release notes (highlights)
Release date: 2025-10-24. [1]
What changed vs 3.9.0 → 3.9.1: mostly dependency bumps, including:
org.apache.kafka:kafka-clients→ 3.9.1co.fs2:fs2-core→ 3.12.2org.typelevel:cats-effect→ 3.6.3- (plus build/tooling updates and Confluent Avro serializer bump in the vulcan module) [1]
Compatibility
Binary compatibility (library):
- fs2-kafka guarantees backward binary compatibility across minor + patch versions within the same major (3.x) (milestones excluded). [2]
Scala / Cats-Effect / FS2 / Kafka client compatibility (3.9.1):
- Scala: 2.12, 2.13, 3.3 [2]
- FS2: 3.12.2 [2]
- Kafka clients: 3.9.1 [2]
- Series matrix: fs2-kafka 3.x is for cats-effect/fs2 3.x and kafka-clients 3.x. [3]
Kafka 3.9.1 note (upstream):
- Apache Kafka 3.9.1 is a bugfix release and adds Java 23 support. [4]
Sources: GitHub release v3.9.1 [1], FS2 Kafka docs overview/compatibility table [2], Scala Index version matrix [3], Apache Kafka 3.9.1 announcement [4].
Flag doobie 1.0.0-RC11 as a release candidate — test Postgres JSON arrays and Scala 3 enums.
The non-RC upgrades are safe: cats-effect 3.6.3 and fs2 3.12.2 are bugfix releases with no breaking changes; fs2-kafka 3.9.1 is a dependency-bump release backward-compatible within the 3.x series. However, doobie 1.0.0-RC11 is a release candidate (pre-release), not a final version. While targeted and low-churn, it introduces two user-facing features (Postgres JSON array mappings and Scala 3 enum derivation) that require integration testing before merging. Run tests on Postgres JSON/JSONB array handling and Scala 3 enum-derived Read/Write instances if you use those features.
🤖 Prompt for AI Agents
In `@project/Versions.scala` around lines 3 - 7, The doobie version in
Versions.scala is set to a release candidate (val doobie = "1.0.0-RC11"); mark
this as an RC in the PR notes and do not treat it as a final upgrade until
validated, then run integration tests that exercise Postgres JSON/JSONB array
mappings and Scala 3 enum-derived Read/Write instances (or any codepaths using
those features) to confirm compatibility before merging; if tests fail or you
rely on those features, either pin back to the previous stable doobie version or
add targeted test coverage and a follow-up task to revisit doobie after a final
release.
soujiro32167
left a comment
soujiro32167
left a comment
There was a problem hiding this comment.
LGTM. I'd also bump up the tapir version to 1.13
|
Oh no not the t-word. No problem, will push an update shortly
…On Wednesday, 4 February 2026, Eli Kasik ***@***.***> wrote:
***@***.**** approved this pull request.
LGTM. I'd also bump up the tapir version to 1.13
—
Reply to this email directly, view it on GitHub
<#52 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA4K5HADQZNMF7NYX7FALDD4KJGUNAVCNFSM6AAAAACT3GUC7SVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZTONJSHAZTMNRXGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
2 participants
also, scala version updates
Summary by CodeRabbit
Chores
Refactor