Fetch 3.1.0 is mostly the same as Fetch 3.0.0, but rolls back a behavioral change from 3.0.0. It does not introduce any breaking changes and the API remains the same.

In Fetch 3.0.0, fixing a bug introduced with the release of Cats 2.7.0 a few months back lead us to believe that it would be better for the library going forward to not explicitly guarantee auto-batching fetch requests when using Cats syntax methods such as .traverse or .sequence. The reason this bug got introduced was because fetch auto-batching behavior depended on certain Cats implementation details that unexpectedly changed. We put together a quick fix shortly after the release of 3.0.0, initially for another 2.x series release, but we have decided to continue the 3.x line instead. Documentation has been updated to reflect that now on versions >=3.1.0 you will still get implicit batching where possible, though it still might go away in the future.

In short, you will continue to get automatic batching on calls to .sequence and .traverse with Fetch 3.1.0 and going forward, in addition to the new syntax we added previously which will stay for backwards compatibility.

In the meantime, please follow 47 Degrees on Twitter and stay up-to-date on our blog for future updates as we have exciting news for Fetch users coming soon on future, related developments.

What's changed

• Update sbt to 1.6.2 (#599) @47erbot
• Update jedis to 4.1.1 (#600) @47erbot
• Update scalafmt-core to 3.4.0 (#597) @47erbot
• Update cats-effect to 3.3.5 (#598) @47erbot
• Update http4s-blaze-client, http4s-circe to 0.23.9 (#595) @47erbot

🐛 Bug Fixes

• Add map2Eval override (#594) @sloshy

Contributors to this release

@47erbot and @sloshy