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.
1.5.15 January 9th 2024
Akka.NET v1.5.15 is a significant release for Akka.NET with some major feature additions and changes.
Akka.Analyzers
- Roslyn Analysis for Akka.NETStartEntity
andShardEnvelope
handlingClusterClient
messages be serialized usingClusterClientMessageSerializer
LocalSnapshotStore
Metadata Fetch to ensure persistenceid match.ProducerControllerImpl<T>
state bug(6.0,]
.INoSerializationVerificationNeeded
does not handleIWrappedMessage
correctlyAkka.Analyzers
The core Akka NuGet package now references Akka.Analyzers, a new set of Roslyn Code Analysis and Code Fix Providers that we distribute via NuGet. You can see the full set of supported Akka.Analyzers rules here.
Akka.Cluster.Sharding Changes
In #6863 we made some major changes to the Akka.Cluster.Sharding API aimed at helping improve Cluster.Sharding's performance and ease of use. However, these changes may require some effort on the part of the end user in order to take full advantage:
ExtractEntityId
andExtractShardId
have been deprecated as they fundamentally can't be extended and can't benefit from the performance improvements introduced into Akka.NET v1.5.15. It is imperative that you migrate to using theHashCodeMessageExtractor
instead.ShardRegion.StartEntity
orShardingEnvelope
inside yourIMessageExtractor
implementations, and in factAK2001
(part of Akka.Analyzers) will automatically detect this and remove those handlers for you. Akka.NET automatically handles these two message types internally now.ClusterClient Serialization Changes
In #7032 we solved a long-standing serialization problem with the
ClusterClient
whereSend
,SendToAll
, andPublish
were not handled by the correct internal serializer. This has been fixed by default in Akka.NET v1.5.15, but this can potentially cause wire compatibility problems during upgrades - therefore we have introduced a configuration setting to toggle this:That setting is currently set to
on
by default, so v1.5.15 will still behave like previous versions of Akka.NET. However, if you have been affected by serialization issues with theClusterClient
(such as #6803) you should toggle this setting tooff
.See "Akka.NET v1.5.15 Upgrade Advisories" for full details on some of the things you might need to do while upgrading to this version of Akka.NET.
You can see the full set of changes for Akka.NET v1.5.15 here.