Skip to content
This repository was archived by the owner on Mar 17, 2025. It is now read-only.

Update dependency dev.zio:zio to v2.1.16 #692

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update dependency dev.zio:zio to v2.1.16 #692

wants to merge 1 commit into from
+1 −1

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 5, 2025 •
edited
Loading

This PR contains the following updates:

Package Update Change
dev.zio:zio (source) patch 2.1.14 -> 2.1.16

Release Notes

zio/zio (dev.zio:zio)

v2.1.16: 2.1.16

Compare Source

Highlights

This seemingly small release brings 2 new features to ZIO which library authors can utilize in order to provide a better DX for users. As usually, it also contains a number of optimizations, bug fixes, and it's fully binary and source-compatible with the rest of the v2.x series.

HasNoScope evidence (https://github.com/zio/zio/pull/9604)

In ZIO, having a Scope as an environment requirement indicates that the effect contains finalizers (e.g., closing an HTTP connection) which need to be handled at some point in the evaluation of the effect or the application's lifetime. In certain cases, we might want to ensure that an effect provided to a method does not contain any finalizers. Starting with this version of ZIO, users / library authors can use the HasNoScope evidence for methods where the environment is generic, e.g.,:

def foo[R, A](f: ZIO[R, Nothing, A)(using HasNoScope[R]) = ???

val f1 = foo(ZIO.succeed("foo")) // compiles
val f2 = foo(ZIO.acquireRelease(ZIO.succeed("foo"))(_ => ZIO.unit)) // fails to compile

Note that this feature is primarily intended for use in libraries such as zio-http where we need to ensure that a user-provided effect does not contain any finalizers.

Generic interfaces for non-empty collections (https://github.com/zio/zio/pull/9560)

This release introduces the NonEmptySeq type class (which NonEmptyChunk now extends) so that users / library authors can write generic code which requires non-empty collections as arguments.

What's Changed

Other changes (CI, dependencies and documentation)

Full Changelog: zio/zio@v2.1.15...v2.1.16

v2.1.15: 2.1.15

Compare Source

Highlights

This release contains various under-the-hood optimizations and minor bug fixes.

[!IMPORTANT]
One noteable change is the update of izumi-reflect to v3.x from v2.x. This version of izumi-reflect generates tags that are not binary/backwards compatible for Scala 3 opaque types with those generated by v2.x.

Since zio itself does not use opaque types, we considered this as a safe change. However, library authors that have ZIO as a dependency might want to check whether this change affects them in any way and release a new version using the updated zio / izumi-reflect versions

What's Changed

Other changes (CI, dependencies and documentation)

New Contributors

Full Changelog: zio/zio@v2.1.14...v2.1.15

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Sorry, something went wrong.

@renovate renovate bot force-pushed the renovate/dev.zio-zio-2.x branch from 4be25ef to c29c8ec Compare February 26, 2025 10:14
@renovate renovate bot changed the title Update dependency dev.zio:zio to v2.1.15 Update dependency dev.zio:zio to v2.1.16 Feb 26, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
0 participants