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.4.13 December 16 2020
Maintenance Release for Akka.NET 1.4
Akka.NET v1.4.13 includes a number of bug fixes and enhancements:
AppVersion
now uses Assembly Version by DefaultThe new
AppVersion
setting, which is used to communicate application version numbers throughout Akka.Cluster and is used in scenarios such as Akka.Cluster.Sharding to help determine which nodes receive new shard allocations and which ones do not, now uses the following default HOCON setting:By default now the
AppVersion
communicated inside Akka.ClusterMember
events uses theMajor.Minor.BuildNumber
from theAssembly.GetEntryssembly()
orAssembly.GetExecutingAssembly()
(in case theEntryAssembly
isnull
). That way any updates made to your executable's (i.e. the .dll that hostsProgram.cs
) version number will be automatically reflected in the cluster now without Akka.NET developers having to set an additional configuration value during deployments.Other bug fixes and improvements:
PatternMatch
KeyNotFoundException
thrown periodicallyTo see the full set of fixes in Akka.NET v1.4.13, please see the milestone on Github.