Update dependency dev.zio:zio to v2.1.14 #437
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/dev.zio-zio-2.x
branch
from
0233c3c to
4f01bbd
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/dev.zio-zio-2.x
branch
from
4f01bbd to
ee26301
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/dev.zio-zio-2.x
branch
from
ee26301 to
682bcbb
Compare
renovate
bot
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.1.8->2.1.14Release Notes
zio/zio (dev.zio:zio)
v2.1.14: 2.1.14Compare Source
Highlights
This release comes packed with bug fixes and under-the-hood optimizations. Big thank you to all the old and new contributors for their work in this release!
What's Changed
Exitoptimizations forZIOmethods (#9427) @kyri-petrouExit.Successfirst inFiberRuntime#runloop(#9422) @kyri-petrouZIO#foreach*methods (#9365) @kyri-petrouExitforPromise.succeed(#9419) @kyri-petrouExit.succeedin more places (#9418) @kyri-petrouTrace.instance.unapplycalls withTrace.instance.parse(#9416) @guizmaiiTracer.instance#unapply(#9414) @guizmaiiZIO/Exitmethods (#9415) @kyri-petrouZIO.suspendSucceedwithZIO.FlatMap(#9388) @guizmaiiflatmap.firstwhen possible (#9393) @guizmaiizio.stream.ZStream.fromChunk(#9396) @guizmaiizio.stream.ZStream.succeed(#9399) @guizmaiiFiberRef#set(#9402) @guizmaiiZIO.Continuationallocation (#9391) @guizmaiiZChannel.mapOutZIOPar*methods (#9354) @kyri-petrouFiberRefsshortcut optimizations (#9328) @kyri-petrouZStream.repeatZIOChunkOption(#9379) @guizmaiiZIO.done(#9369) @kyri-petrouPull.failCausecode (#9364) @guizmaiiZIO.success(Chunk.empty)calls withExit.emptyChunk(#9360) @guizmaiiZIO.fail(None)withExit.failNone(#9359) @guizmaiiZKeyedPool(#9329) @kyri-petrouvals non-transient in ZIO services (#9345) @kyri-petrou-Ybackend-parallelism:4when compiling Scala 2.13 with optimization enabled (#9346) @kyri-petrouapplyOnExitandapplyOnExitWithmethods toZIO.Grafter(#9349) @kyri-petrouvalfor accessingRef.Atomic#unsafe(#9344) @kyri-petrouZStream#runScoped(#9327) @kyri-petrouOther changes (CI, dependencies and documentation)
New Contributors
Full Changelog: zio/zio@v2.1.13...v2.1.14
v2.1.13: 2.1.13Compare Source
Highlights
This seemingly small release brings a number of new features and important bugfixes:
zio-test-junit-enginemodule #9214.zio.Systemin JS engines that support it (e.g., NodeJS) #9282.ZStream.mapZIOPar*methods since v2.1.12 #9312.As always, this version is fully source and binary compatible with the rest of the v2.x series.
What's Changed
WhileLoops by @kyri-petrou in https://github.com/zio/zio/pull/9289ZKeydPool#invalidateby @kyri-petrou in https://github.com/zio/zio/pull/9307ZChannel#mapOutPar*methods by @kyri-petrou in https://github.com/zio/zio/pull/9312Other changes (CI, dependencies and documentation)
New Contributors
Full Changelog: zio/zio@v2.1.12...v2.1.13
v2.1.12: 2.1.12Compare Source
This release brings a couple bug fixes for
STM, as well as a few optimizations and usability improvements.What's Changed
ZIO.fromNullableby @kyri-petrou in https://github.com/zio/zio/pull/9250Fiber.Runtime.UnsafeAPI#interruptmethod by @hearnadam in https://github.com/zio/zio/pull/9246suiteAllfor Scala 3 by @kyri-petrou in https://github.com/zio/zio/pull/9273TMap#toMapidempotent by @kyri-petrou in https://github.com/zio/zio/pull/9280Other changes (CI, dependencies and documentation)
.devcontainerconfig by @kyri-petrou in https://github.com/zio/zio/pull/9228ZStream.fromOutputStreamScopedby @kyri-petrou in https://github.com/zio/zio/pull/9269Accessor Methodssection from it by @guizmaii in https://github.com/zio/zio/pull/9220v2.1.11: 2.1.11Compare Source
We found a regression in 2.1.10 causing a runtime exception in some cases when using ZIO environment and layers, so here's a release to fix that.
What's Changed
IndexOutOfBoundsExceptionwhen usingreverseIteratoronUpdateOrderLinkedMapby @kyri-petrou in https://github.com/zio/zio/pull/9239v2.1.10: 2.1.10Compare Source
This release brings a few important bug fixes related to
ZPoolandZSTMas well as some optimizations. It also fixes a binary incompatibility that caused runtime errors when using an older version ZIO Streams together with ZIO 2.1.9.Important note about ZPool changes
There are 2 fixes / changes to ZPool that might affect the behaviour of an application so users are advised to revise the following in cases of unexpected behaviour after upgrading to ZIO 2.1.10+.
Eager / strict initialization of ZPool's resources
In previous ZIO versions, the initialization of ZPool resources was done lazily in a daemon fiber. e.g., this code would previously print the message, but will now "hang" awaiting for the pool to be initialized to its full size:
We believe that this change makes the behaviour of ZPool more predictable (and referentially transparent!) as previously there were no guarantees that the ZPool resources would be initialized during the creation of the pool. However, this might result in the initialization of the pool hanging in cases that the acquisition of the resources itself hangs. Therefore users are advised to consider adding timeouts to the resource initialization effect.
Strict finalization of ZPool resources
In previous versions, it was possible for the ZPool finalizers to be interrupted, which would lead to potential leak of resources (see this issue for more info). Starting with ZIO 2.1.10+, closing a ZPool requires all of the resource finalizers to finish first. As with (1), this might lead to some unexpected behaviour if the finalization of a resource hangs indefinitely, so users are advised to add timeouts to the finalizers of resources used with ZPool.
What's Changed
Ref.Atomicby @kyri-petrou in https://github.com/zio/zio/pull/9155ZEnvironmentwhen applying optimizations by @kyri-petrou in https://github.com/zio/zio/pull/9207Other changes (CI, dependencies and documentation)
v2.1.9: 2.1.9Compare Source
After receiving multiple reports of users failing to compile code using
ZLayermacros with v2.1.8, we decided to temporarily revert https://github.com/zio/zio/pull/9077 until we get to bottom of what's been causing it.What's Changed
Full Changelog: zio/zio@v2.1.8...v2.1.9
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.
This PR was generated by Mend Renovate. View the repository job log.