Bump the akka group with 2 updates#1560
Merged
Merged
Conversation
Bumps Akka.Cluster.Sharding from 1.5.69 to 1.5.70 Bumps Akka.Persistence from 1.5.69 to 1.5.70 --- updated-dependencies: - dependency-name: Akka.Cluster.Sharding dependency-version: 1.5.70 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: akka - dependency-name: Akka.Persistence dependency-version: 1.5.70 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: akka ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
Bot
added
.NET
Collaborator
|
@dependabot update |
Aaronontheweb
enabled auto-merge (squash)
July 3, 2026 11:57
Aaronontheweb
disabled auto-merge
July 3, 2026 13:53
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
1 participant
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.
Rebasing might not happen immediately, so don't worry if this takes some time.
Note: if you make any changes to this PR yourself, they will take precedence over the rebase.
Updated Akka.Cluster.Sharding from 1.5.69 to 1.5.70.
Release notes
Sourced from Akka.Cluster.Sharding's releases.
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.
Updated Akka.Persistence from 1.5.69 to 1.5.70.
Release notes
Sourced from Akka.Persistence's releases.
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.
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