deps: Bump Akka.Hosting, Akka.Streams.TestKit and Akka.TestKit.Xunit - #87
Open
dependabot[bot] wants to merge 1 commit into
Open
deps: Bump Akka.Hosting, Akka.Streams.TestKit and Akka.TestKit.Xunit#87dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps Akka.Hosting from 1.5.68 to 1.5.71 Bumps Akka.Streams.TestKit from 1.5.68 to 1.5.71 Bumps Akka.TestKit.Xunit from 1.5.68 to 1.5.71 --- updated-dependencies: - dependency-name: Akka.Hosting dependency-version: 1.5.71 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: akka - dependency-name: Akka.Streams.TestKit dependency-version: 1.5.71 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: akka - dependency-name: Akka.TestKit.Xunit dependency-version: 1.5.71 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: akka ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
.NET
This file contains hidden or 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
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.
Pinned Akka.Hosting at 1.5.71.
Release notes
Sourced from Akka.Hosting's releases.
1.5.71
1.5.71 August 26th 2026
Updates
1.5.70
1.5.70 July 2nd 2026
Updates
1.5.69
1.5.69 June 15th 2026
Updates
Commits viewable in compare view.
Updated Akka.Streams.TestKit from 1.5.68 to 1.5.71.
Release notes
Sourced from Akka.Streams.TestKit's releases.
1.5.71
1.5.71 August 26th, 2026
Akka.NET v1.5.71 is a maintenance release that fixes a Cluster Sharding private-replicator recovery bug, hardens MultiNodeTestRunner conductor reliability, flushes graceful
DisassociatePDUs before transport force-close on shutdown, and resolves a handful of TestKit, ClusterClientDiscovery, and DotNetty fixes.Akka.Cluster.Sharding
ClusterShardingReplicatorResiliencySpeccovering the recovery path.Akka.Remote
DisassociatePDUs before transport force-close on shutdown: Ensures in-flight gracefulDisassociatecontrol messages are flushed to the wire before the transport force-closes the connection on shutdown, preventing an abrupt teardown from silently dropping them.Akka.Remote.TestKit (MultiNodeTestRunner)
BarrierCoordinator,Conductor,Controller,Player, andRemoteConnectionagainst conductor-side races and disconnect handling, reducing multi-node spec flakiness.Akka.TestKit
PromiseActorRef.GetPaththat madePathreturn null: Fixes a torn read inPromiseActorRef.GetPaththat could returnnullunder concurrent access.ExpectMsgAsync<T>(Func<T, IActorRef, bool>, ...): Fixes a bug where the overload ofExpectMsgAsyncthat takes a predicate could apply its timeout dilation twice, causing spurious timeout failures.Akka.Cluster.Tools
ClusterClientDiscoverykeeps its contact-point subscriptions alive across rediscovery cycles instead of dropping them.Tests
ClusterShardingQueriesSpecstats/region-state queries converge-then-assert (async): HardensClusterShardingQueriesSpecby making its stats and region-state query assertions wait for convergence before asserting, reducing CI flakiness.1 contributor since release 1.5.70
To see the full set of changes in Akka.NET v1.5.71, click here.
Changes:
See More
... (truncated)
1.5.70
1.5.70 July 2nd, 2026
Akka.NET v1.5.70 is a maintenance release that adds a new "last-N" query offset to Akka.Persistence.Query, resolves two Akka.Streams reliability issues and improves
BroadcastHubperformance under high consumer counts, and fixes a consistent-hashing router bug that could wedge an entire cluster after a 32-bit hash collision.Akka.Persistence.Query
Offset.FromEnd(int count)— "last-N events" query offset: IntroducesOffset.FromEnd(int count), a new query-input-only offset type that begins a read journal query at the Nth event from the end of history rather than from the beginning. The offset is resolved at stream materialization into a concreteSequencestart position; no interface changes or wire-format changes are required. Includes opt-in TCK spec (FromEndOffsetSpec) for plugin authors.Akka.Streams Bug Fixes
Source.From(IAsyncEnumerable<T>)where the underlying enumerator could be disposed before all elements were delivered to downstream, causingObjectDisposedExceptionon high-throughput pipelines.ChannelSinkdrops final element on backpressure - Fixes #8285:ChannelSinkwas discarding the last element in a sequence whenever the downstreamChannel<T>applied backpressure during completion. The sink now correctly delivers all elements before signaling completion.Akka.Streams Performance
BroadcastHubwhen many consumers are attached by optimizing the internal consumer-wheel iteration, yielding measurable throughput improvements at high fan-out.Akka.Core Bug Fixes
ConsistentHash.Createthrew"An entry with the same key already exists". The consistent-hashing router swallowed the exception and returnedNoRouteefor every subsequent message until a manual restart. The ring now linear-probes to the next free slot on a collision instead of throwing. This keeps the hash distribution unchanged and produces a byte-identical ring to prior versions whenever no collision occurs (safe for rolling upgrades), and also protectsAkka.Cluster.Tools'ClusterReceptionist, which builds the same ring.2 contributors since release 1.5.69
To see the full set of changes in Akka.NET v1.5.70, click here.
Changes:
See More
... (truncated)
1.5.70-beta2
1.5.70-beta2 June 30th, 2026
Akka.NET v1.5.70-beta2 is a beta release with a bug fix for
ChannelSinkdropping the final element under backpressure.Akka.Streams Bug Fixes
ChannelSinkdrops final element on backpressure - Fixes #8285:ChannelSinkwas discarding the last element in a sequence whenever the downstreamChannel<T>applied backpressure during completion. The sink now correctly delivers all elements before signaling completion.2 contributors since release 1.5.70-beta1
Changes:
This list of changes was auto generated.
1.5.70-beta1
1.5.70-beta1 June 23rd, 2026
Akka.NET v1.5.70-beta1 is a beta release with a new
Offset.FromEndquery offset for Akka.Persistence.Query, bug fixes forAkka.Streamsasync enumerable disposal, and a performance improvement forBroadcastHubwith high consumer counts.Akka.Persistence.Query
Offset.FromEnd(int count)— "last-N events" query offset: IntroducesOffset.FromEnd(int count), a new query-input-only offset type that begins a read journal query at the Nth event from the end of history rather than from the beginning. The offset is resolved at stream materialization into a concreteSequencestart position; no interface changes or wire-format changes are required. Includes opt-in TCK spec (FromEndOffsetSpec) for plugin authors.Akka.Streams Bug Fixes
Source.From(IAsyncEnumerable<T>)where the underlying enumerator could be disposed before all elements were delivered to downstream, causingObjectDisposedExceptionon high-throughput pipelines.Akka.Streams Performance
BroadcastHubwhen many consumers are attached by optimizing the internal consumer-wheel iteration, yielding measurable throughput improvements at high fan-out.1 contributor since release 1.5.69
Changes:
This list of changes was auto generated.
1.5.69
1.5.69 June 12th, 2026
Akka.NET v1.5.69 is a maintenance release with bug fixes for Akka.DistributedData state propagation, Akka.Core message rejection handling, and Akka.Streams tracing reliability and backpressure cancellation.
Akka.Streams
.Async()actor boundary - Fixes #8243: With stream tracing enabled, per-element trace context was dropped at the publisher/subscriber actor boundary introduced by.Async(), leaving downstream stages with no ambientActivityContext. Trace context now flows correctly across fused interpreter shells.OfferAsync(T, CancellationToken)toISourceQueue<T>— enables cancellation of backpressured pending offers without emitting the cancelled element.Akka.Streams Bug Fixes
NullReferenceExceptionin theGraphInterpreterwhen tracing across actor boundaries — the interpreter now safely handles null activity context references during stream teardown.Akka.Core
RejectOnType<TMessage>should useRejection, notFailure- Fixes #8231:RejectOnTypenow correctly wraps rejected messages asRejectionrather than throwing aFailure, matching the expected stream contract.Akka.DistributedData
ORSetandLWWDictionary, leading to data inconsistencies during node merges.1 contributor since release 1.5.68
Akka.NET v1.5.68 is a maintenance release with bug fixes for Akka.IO TCP connection handling, Akka.Streams stream materialized task faults, and Akka.TestKit xUnit 3 parallel context management.
Akka.IO Bug Fixes
Tcp.CommandFailedwhen a scheduled connect retry throws - Fixes #8195: On Linux, a dropped TCP connection could permanently stall the user actor — it never receivedTcp.ConnectedorTcp.CommandFailedbecause aPlatformNotSupportedExceptionthrown during a scheduled connect retry was swallowed by theHashedWheelTimerScheduler. The retry is now scheduled as aRetryConnectself-message viaIWithTimers, ensuring any exception is surfaced to the commander asTcp.CommandFailedand the connection actor stops cleanly. The pending timer is also canceled automatically when the actor stops, removing a latent use-after-dispose bug.Akka.Streams Bug Fixes
IgnoreSink,QueueSource, andLazySinknow observe their internal materializedTaskfaults, preventing them from surfacing later asUnobservedTaskExceptionevents on the thread pool.Akka.TestKit Bug Fixes
SynchronizationContextinActorCellKeepingSynchronizationContext-ActorCellKeepingSynchronizationContextnow accepts an optional innerSynchronizationContextand delegates scheduling to it while wrapping callbacks with the cell-pinning window. This prevents test hangs in downstream consumers such asAkka.Hosting.TestKitwhose asyncIHostlifecycle depends on xUnit v3'sMaxConcurrencySyncContextscheduling.1 contributor since release 1.5.67
To see the full set of changes in Akka.NET v1.5.68, click here.
Changes:
... (truncated)
Commits viewable in compare view.
Updated Akka.TestKit.Xunit from 1.5.68 to 1.5.71.
Release notes
Sourced from Akka.TestKit.Xunit's releases.
1.5.71
1.5.71 August 26th, 2026
Akka.NET v1.5.71 is a maintenance release that fixes a Cluster Sharding private-replicator recovery bug, hardens MultiNodeTestRunner conductor reliability, flushes graceful
DisassociatePDUs before transport force-close on shutdown, and resolves a handful of TestKit, ClusterClientDiscovery, and DotNetty fixes.Akka.Cluster.Sharding
ClusterShardingReplicatorResiliencySpeccovering the recovery path.Akka.Remote
DisassociatePDUs before transport force-close on shutdown: Ensures in-flight gracefulDisassociatecontrol messages are flushed to the wire before the transport force-closes the connection on shutdown, preventing an abrupt teardown from silently dropping them.Akka.Remote.TestKit (MultiNodeTestRunner)
BarrierCoordinator,Conductor,Controller,Player, andRemoteConnectionagainst conductor-side races and disconnect handling, reducing multi-node spec flakiness.Akka.TestKit
PromiseActorRef.GetPaththat madePathreturn null: Fixes a torn read inPromiseActorRef.GetPaththat could returnnullunder concurrent access.ExpectMsgAsync<T>(Func<T, IActorRef, bool>, ...): Fixes a bug where the overload ofExpectMsgAsyncthat takes a predicate could apply its timeout dilation twice, causing spurious timeout failures.Akka.Cluster.Tools
ClusterClientDiscoverykeeps its contact-point subscriptions alive across rediscovery cycles instead of dropping them.Tests
ClusterShardingQueriesSpecstats/region-state queries converge-then-assert (async): HardensClusterShardingQueriesSpecby making its stats and region-state query assertions wait for convergence before asserting, reducing CI flakiness.1 contributor since release 1.5.70
To see the full set of changes in Akka.NET v1.5.71, click here.
Changes:
See More
... (truncated)
1.5.70
1.5.70 July 2nd, 2026
Akka.NET v1.5.70 is a maintenance release that adds a new "last-N" query offset to Akka.Persistence.Query, resolves two Akka.Streams reliability issues and improves
BroadcastHubperformance under high consumer counts, and fixes a consistent-hashing router bug that could wedge an entire cluster after a 32-bit hash collision.Akka.Persistence.Query
Offset.FromEnd(int count)— "last-N events" query offset: IntroducesOffset.FromEnd(int count), a new query-input-only offset type that begins a read journal query at the Nth event from the end of history rather than from the beginning. The offset is resolved at stream materialization into a concreteSequencestart position; no interface changes or wire-format changes are required. Includes opt-in TCK spec (FromEndOffsetSpec) for plugin authors.Akka.Streams Bug Fixes
Source.From(IAsyncEnumerable<T>)where the underlying enumerator could be disposed before all elements were delivered to downstream, causingObjectDisposedExceptionon high-throughput pipelines.ChannelSinkdrops final element on backpressure - Fixes #8285:ChannelSinkwas discarding the last element in a sequence whenever the downstreamChannel<T>applied backpressure during completion. The sink now correctly delivers all elements before signaling completion.Akka.Streams Performance
BroadcastHubwhen many consumers are attached by optimizing the internal consumer-wheel iteration, yielding measurable throughput improvements at high fan-out.Akka.Core Bug Fixes
ConsistentHash.Createthrew"An entry with the same key already exists". The consistent-hashing router swallowed the exception and returnedNoRouteefor every subsequent message until a manual restart. The ring now linear-probes to the next free slot on a collision instead of throwing. This keeps the hash distribution unchanged and produces a byte-identical ring to prior versions whenever no collision occurs (safe for rolling upgrades), and also protectsAkka.Cluster.Tools'ClusterReceptionist, which builds the same ring.2 contributors since release 1.5.69
To see the full set of changes in Akka.NET v1.5.70, click here.
Changes:
See More
... (truncated)
1.5.70-beta2
1.5.70-beta2 June 30th, 2026
Akka.NET v1.5.70-beta2 is a beta release with a bug fix for
ChannelSinkdropping the final element under backpressure.Akka.Streams Bug Fixes
ChannelSinkdrops final element on backpressure - Fixes #8285:ChannelSinkwas discarding the last element in a sequence whenever the downstreamChannel<T>applied backpressure during completion. The sink now correctly delivers all elements before signaling completion.2 contributors since release 1.5.70-beta1
Changes:
This list of changes was auto generated.
1.5.70-beta1
1.5.70-beta1 June 23rd, 2026
Akka.NET v1.5.70-beta1 is a beta release with a new
Offset.FromEndquery offset for Akka.Persistence.Query, bug fixes forAkka.Streamsasync enumerable disposal, and a performance improvement forBroadcastHubwith high consumer counts.Akka.Persistence.Query
Offset.FromEnd(int count)— "last-N events" query offset: IntroducesOffset.FromEnd(int count), a new query-input-only offset type that begins a read journal query at the Nth event from the end of history rather than from the beginning. The offset is resolved at stream materialization into a concreteSequencestart position; no interface changes or wire-format changes are required. Includes opt-in TCK spec (FromEndOffsetSpec) for plugin authors.Akka.Streams Bug Fixes
Source.From(IAsyncEnumerable<T>)where the underlying enumerator could be disposed before all elements were delivered to downstream, causingObjectDisposedExceptionon high-throughput pipelines.Akka.Streams Performance
BroadcastHubwhen many consumers are attached by optimizing the internal consumer-wheel iteration, yielding measurable throughput improvements at high fan-out.1 contributor since release 1.5.69
Changes:
This list of changes was auto generated.
1.5.69
1.5.69 June 12th, 2026
Akka.NET v1.5.69 is a maintenance release with bug fixes for Akka.DistributedData state propagation, Akka.Core message rejection handling, and Akka.Streams tracing reliability and backpressure cancellation.
Akka.Streams
.Async()actor boundary - Fixes #8243: With stream tracing enabled, per-element trace context was dropped at the publisher/subscriber actor boundary introduced by.Async(), leaving downstream stages with no ambientActivityContext. Trace context now flows correctly across fused interpreter shells.OfferAsync(T, CancellationToken)toISourceQueue<T>— enables cancellation of backpressured pending offers without emitting the cancelled element.Akka.Streams Bug Fixes
NullReferenceExceptionin theGraphInterpreterwhen tracing across actor boundaries — the interpreter now safely handles null activity context references during stream teardown.Akka.Core
RejectOnType<TMessage>should useRejection, notFailure- Fixes #8231:RejectOnTypenow correctly wraps rejected messages asRejectionrather than throwing aFailure, matching the expected stream contract.Akka.DistributedData
ORSetandLWWDictionary, leading to data inconsistencies during node merges.1 contributor since release 1.5.68
Akka.NET v1.5.68 is a maintenance release with bug fixes for Akka.IO TCP connection handling, Akka.Streams stream materialized task faults, and Akka.TestKit xUnit 3 parallel context management.
Akka.IO Bug Fixes
Tcp.CommandFailedwhen a scheduled connect retry throws - Fixes #8195: On Linux, a dropped TCP connection could permanently stall the user actor — it never receivedTcp.ConnectedorTcp.CommandFailedbecause aPlatformNotSupportedExceptionthrown during a scheduled connect retry was swallowed by theHashedWheelTimerScheduler. The retry is now scheduled as aRetryConnectself-message viaIWithTimers, ensuring any exception is surfaced to the commander asTcp.CommandFailedand the connection actor stops cleanly. The pending timer is also canceled automatically when the actor stops, removing a latent use-after-dispose bug.Akka.Streams Bug Fixes
IgnoreSink,QueueSource, andLazySinknow observe their internal materializedTaskfaults, preventing them from surfacing later asUnobservedTaskExceptionevents on the thread pool.Akka.TestKit Bug Fixes
SynchronizationContextinActorCellKeepingSynchronizationContext-ActorCellKeepingSynchronizationContextnow accepts an optional innerSynchronizationContextand delegates scheduling to it while wrapping callbacks with the cell-pinning window. This prevents test hangs in downstream consumers such asAkka.Hosting.TestKitwhose asyncIHostlifecycle depends on xUnit v3'sMaxConcurrencySyncContextscheduling.1 contributor since release 1.5.67
To see the full set of changes in Akka.NET v1.5.68, click here.
Changes:
... (truncated)
Commits viewable 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions