Bump Akka.Persistence.TCK from 1.5.69 to 1.5.71 - #25
Merged
github-actions[bot] merged 1 commit intoAug 30, 2026
Merged
Conversation
dependabot
Bot
added
.NET
--- updated-dependencies: - dependency-name: Akka.Persistence.TCK dependency-version: 1.5.71 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/nuget/Akka.Persistence.TCK-1.5.71
branch
from
August 30, 2026 01:39
3adf59c to
a6d0db1
Compare
github-actions
Bot
deleted the
dependabot/nuget/Akka.Persistence.TCK-1.5.71
branch
August 30, 2026 01:40
thomas-stegemann
pushed a commit
that referenced
this pull request
Sep 19, 2026
--- updated-dependencies: - dependency-name: Akka.Persistence.TCK dependency-version: 1.5.71 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
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.
Updated Akka.Persistence.TCK from 1.5.69 to 1.5.71.
Release notes
Sourced from Akka.Persistence.TCK'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.
Commits viewable in compare view.