build: Bump Akka.Hosting, Akka.Streams.TestKit and Akka.TestKit.Xunit#56
Merged
Conversation
Bumps Akka.Hosting from 1.5.65 to 1.5.67 Bumps Akka.Streams.TestKit from 1.5.65 to 1.5.67 Bumps Akka.TestKit.Xunit from 1.5.65 to 1.5.67 --- updated-dependencies: - dependency-name: Akka.Hosting dependency-version: 1.5.67 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: akka - dependency-name: Akka.Streams.TestKit dependency-version: 1.5.67 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: akka - dependency-name: Akka.TestKit.Xunit dependency-version: 1.5.67 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: akka ... Signed-off-by: dependabot[bot] <support@github.com>
a669998 to
b4a1e42
Compare
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.67.
Release notes
Sourced from Akka.Hosting's releases.
1.5.67
1.5.67 April 26th 2026
New Features
WithStrictSerializationhelper — resolves issue #734. AddsWithStrictSerialization(bool enabled = true)extension onAkkaConfigurationBuilderthat setsakka.actor.serialization-settings.allow-unregistered-types = off, disabling the Newtonsoft.Json fallback and throwingSerializationExceptionfor unregistered types.Updates
Commits viewable in compare view.
Updated Akka.Streams.TestKit from 1.5.65 to 1.5.67.
Release notes
Sourced from Akka.Streams.TestKit's releases.
1.5.67
1.5.67 April 25th, 2026
Akka.NET v1.5.67 is a hotfix release that reverts a breaking change to the persistence plugin contract introduced in v1.5.66.
Akka.Persistence: Revert async
WriteMessagesAsync/SaveAsyncdispatch (#8163)v1.5.66 added
Task.Yield()insideAsyncWriteJournal.ExecuteBatchandSnapshotStoreto move persistence pluginWriteMessagesAsync/SaveAsynccalls off the actor thread. While this improved throughput in benchmarks, it silently broke the implicit contract that persistence plugins rely on — that the synchronous preamble of these methods executes in actor context.This caused failures in plugins that:
SelfinsideWriteMessagesAsync(e.g. Akka.Persistence.Sql, Akka.Persistence.EventStore) — throwsNotSupportedExceptionoff the actor threadDictionary<string, Task>) — concurrent access from actor thread and thread pool causesInvalidOperationExceptionThis release removes the
Task.Yield()calls and restores the original dispatch behavior. A future version may reintroduce this optimization with a more targeted approach that preserves the plugin threading contract.If you are on v1.5.66, upgrade to v1.5.67 immediately if you use any third-party persistence plugin.
Changes:
This list of changes was auto generated.
1.5.66
1.5.66 April 24th, 2026
Akka.NET v1.5.66 is a significant release with persistence bug fixes, major Akka.Streams improvements including OpenTelemetry trace propagation and non-blocking materialized values, and new serialization security controls.
Akka.Streams: OpenTelemetry Trace Context Propagation
Akka.Streams now propagates
System.Diagnostics.Activitytrace context end-to-end through stream graphs, including across async stage boundaries, fan-in merges, and fan-out broadcasts. This enables full distributed tracing visibility into stream pipelines when using OpenTelemetry.For full documentation, see: https://getakka.net/articles/streams/stream-tracing.html
Akka.Streams: Non-Blocking Materialized-Value TaskCompletionSource
All
TaskCompletionSourceinstances used for materialized values across Akka.Streams now useTaskCreationOptions.RunContinuationsAsynchronously, eliminating potential deadlocks and thread-pool starvation when continuations run synchronously on completion.Akka.Persistence
Akka.Core
New Features
allow-unregistered-typesserialization setting — when set tofalse,FindSerializerForTypethrowsSerializationExceptionif no explicit serializer binding exists, rather than falling back to the default serializer.Documentation
4 contributors since release 1.5.65
To see the full set of changes in Akka.NET v1.5.66, click here.
Changes:
... (truncated)
Commits viewable in compare view.
Updated Akka.TestKit.Xunit from 1.5.65 to 1.5.67.
Release notes
Sourced from Akka.TestKit.Xunit's releases.
1.5.67
1.5.67 April 25th, 2026
Akka.NET v1.5.67 is a hotfix release that reverts a breaking change to the persistence plugin contract introduced in v1.5.66.
Akka.Persistence: Revert async
WriteMessagesAsync/SaveAsyncdispatch (#8163)v1.5.66 added
Task.Yield()insideAsyncWriteJournal.ExecuteBatchandSnapshotStoreto move persistence pluginWriteMessagesAsync/SaveAsynccalls off the actor thread. While this improved throughput in benchmarks, it silently broke the implicit contract that persistence plugins rely on — that the synchronous preamble of these methods executes in actor context.This caused failures in plugins that:
SelfinsideWriteMessagesAsync(e.g. Akka.Persistence.Sql, Akka.Persistence.EventStore) — throwsNotSupportedExceptionoff the actor threadDictionary<string, Task>) — concurrent access from actor thread and thread pool causesInvalidOperationExceptionThis release removes the
Task.Yield()calls and restores the original dispatch behavior. A future version may reintroduce this optimization with a more targeted approach that preserves the plugin threading contract.If you are on v1.5.66, upgrade to v1.5.67 immediately if you use any third-party persistence plugin.
Changes:
This list of changes was auto generated.
1.5.66
1.5.66 April 24th, 2026
Akka.NET v1.5.66 is a significant release with persistence bug fixes, major Akka.Streams improvements including OpenTelemetry trace propagation and non-blocking materialized values, and new serialization security controls.
Akka.Streams: OpenTelemetry Trace Context Propagation
Akka.Streams now propagates
System.Diagnostics.Activitytrace context end-to-end through stream graphs, including across async stage boundaries, fan-in merges, and fan-out broadcasts. This enables full distributed tracing visibility into stream pipelines when using OpenTelemetry.For full documentation, see: https://getakka.net/articles/streams/stream-tracing.html
Akka.Streams: Non-Blocking Materialized-Value TaskCompletionSource
All
TaskCompletionSourceinstances used for materialized values across Akka.Streams now useTaskCreationOptions.RunContinuationsAsynchronously, eliminating potential deadlocks and thread-pool starvation when continuations run synchronously on completion.Akka.Persistence
Akka.Core
New Features
allow-unregistered-typesserialization setting — when set tofalse,FindSerializerForTypethrowsSerializationExceptionif no explicit serializer binding exists, rather than falling back to the default serializer.Documentation
4 contributors since release 1.5.65
To see the full set of changes in Akka.NET v1.5.66, 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