Bump cats-effect_2.12 from 0.4 to 3.0-8096649

[dependabot-preview]

Bumps cats-effect_2.12 from 0.4 to 3.0-8096649.

Release notes

Sourced from cats-effect_2.12's releases.

v2.2.0-RC3

This is the third release candidate for 2.2.0, containing all of the of the changes described in RC2 and RC1. It is fully binary compatible with the entire 2.x release line.

The only change from 2.2.0-RC2 is as follows:

• #1006 - Fix Semaphore#tryAcquireN when acquiring exactly all available permits (@RaasAhsan)

Special thanks to you!

v2.2.0-RC2

This is the second release candidate for 2.2.0, containing all of the changes described in v2.2.0-RC1. This release is fully binary compatible with everything in the 2.x line, and it is expected to be mostly source-compatible, though some source incompatibilities may exist. A minor binary incompatibility exists with 2.2.0-RC1, in the MVar2 API. It is very unlikely that anyone will be affected by this, as it only applies to those who defined a custom MVar2 implementation.

The main reason we are following a release candidate cycle for this particular release is to solicit feedback on tracing, which is the largest new feature in the 2.2.0 line. Please try this out on your codebase and let us know how it works, where it didn't work, and what features or tweaks you would like to see!

The primary changes from 2.2.0-RC1 are as follows:

• #938 - Added IO#map2Eval (@johnynek)
• #912 - Added some additional functions to MVar2 (@vasilmkd)
• #981 - Improved semantic specificity of tracing on combinators (e.g. *>) (@RaasAhsan)
• #930 - Documentation fixes (@RaasAhsan)

Special thanks to each and every one of you!

v2.2.0-RC1

This is the seventh major release in the Cats Effect 2.x lineage and the first release candidate for a minor release in this line. It is fully binary compatible with all 2.x.y releases. As previously noted, this is the first Cats Effect release to be exclusively published for ScalaJS 1.x; there are no 0.6.x cross-releases.

This is a relatively large release with a few major changes, which is why we're following a release candidate process. We expect 2.2.0 final to be released within a few weeks, depending on feedback. Despite the "release candidate" moniker, we do not anticipate any serious issues with this release; please try it out and report any problems as soon as possible!

Notable New Features

Asynchronous Tracing

IO tracing is probably the single most-requested Cats Effect feature, and it's finally here! Thanks to the tireless work of @RaasAhsan, IO now has a basic, high-performance asynchronous tracing mechanism. Note that this mechanism has very different internals from the async tracing already available in Akka and ZIO, and thus comes with a different set of tradeoffs. Also please remember that no async tracing on the JVM is perfectly accurate, and you may see misleading trace frames depending on your program. Despite all this, the added information is very welcome and sometimes quite helpful in tracking down issues!

This is what it looks like:

IOTrace: 13 frames captured, 0 omitted
  ├ flatMap at org.simpleapp.example.Example.run (Example.scala:67)
  ├ flatMap at org.simpleapp.example.Example.program (Example.scala:57)
  ├ flatMap at org.simpleapp.example.Example.program (Example.scala:58)
  ├ flatMap at org.simpleapp.example.Example.program (Example.scala:59)
  ├ flatMap at org.simpleapp.example.Example.program (Example.scala:60)
  ├ async at org.simpleapp.example.Example.program (Example.scala:60)
  ├ flatMap at org.simpleapp.example.Example.program (Example.scala:61)
  ├ flatMap at org.simpleapp.example.Example.program (Example.scala:60)
  ├ flatMap at org.simpleapp.example.Example.program2 (Example.scala:51)
  ├ map at org.simpleapp.example.Example.program2 (Example.scala:52)
  ├ map at org.simpleapp.example.Example.program (Example.scala:60)
  ├ map at org.simpleapp.example.Example.program (Example.scala:62)
</tr></table> ... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[dependabot-preview]

Superseded by #133.