Skip to content

Latest commit

 

History

History
238 lines (158 loc) · 11.4 KB

RELEASE_NOTES.md

File metadata and controls

238 lines (158 loc) · 11.4 KB

[1.5.30.1] / October 18th 2024

[1.5.30] / October 3rd 2024

[1.5.29] / October 1st 2024

Note

Deprecated

Deprecated due to Akka.NET 1.5.29 deprecation. Please use 1.5.30 instead.

[1.5.28] / 4 September 2024

[1.5.27] / 29 July 2024

Note

We added support for cluster client initial contact discovery feature in this feature. To use this feature, you will need to use Akka.Management v1.5.27 or higher.

[1.5.25] / 17 June 2024

[1.5.24] / 10 June 2024

You can now start ShardedDaemonProcess host and proxy using Akka.Hosting through 2 new Akka.Cluster.Hosting extension methods

public static AkkaConfigurationBuilder WithShardedDaemonProcess<TKey>(
   this AkkaConfigurationBuilder builder,
   string name,
   int numberOfInstances,
   Func<ActorSystem, IActorRegistry, IDependencyResolver, Func<int, Props>> entityPropsFactory,
   ClusterDaemonOptions? options = null)
public static AkkaConfigurationBuilder WithShardedDaemonProcessProxy<TKey>(
   this AkkaConfigurationBuilder builder,
   string name,
   int numberOfInstances,
   string role)

[1.5.22] / 4 June 2024

Filtering Logs In Akka.NET

In Akka.NET 1.5.21, we introduced log filtering for log messages based on the LogSource or the content of a log message. Depending on your coding style, you can use this feature in Akka.Hosting in several ways.

  1. Using The LoggerConfigBuilder.WithLogFilter() method.

    The LoggerConfigBuilder.WithLogFilter() method lets you set up the LogFilterBuilder

    builder.Services.AddAkka("MyActorSystem", configurationBuilder =>
    {
        configurationBuilder
            .ConfigureLoggers(loggerConfigBuilder =>
            {
                loggerConfigBuilder.WithLogFilter(filterBuilder =>
                {
                    filterBuilder.ExcludeMessageContaining("Test");
                });
            });
    });
  2. Setting the loggerConfigBuilder.LogFilterBuilder property directly.

    builder.Services.AddAkka("MyActorSystem", configurationBuilder =>
    {
        configurationBuilder
            .ConfigureLoggers(loggerConfigBuilder =>
            {
                loggerConfigBuilder.LogFilterBuilder = new LogFilterBuilder();
                loggerConfigBuilder.LogFilterBuilder.ExcludeMessageContaining("Test");
            });
    });

[1.5.20] / 30 April 2024

  • Update Akka.NET to 1.5.20
  • Added improved APIs for setting default ILogMessageFormatters - the LoggerConfigBuilder.WithDefaultLogMessageFormatter<T> method.

[1.5.19] / 17 April 2024

[1.5.18] / 15 March 2024

[1.5.17.1] / 04 March 2024

[1.5.16] / 23 February 2024

[1.5.15] / 10 January 2024

[1.5.14] / 09 January 2024

[1.5.12.1] / 31 August 2023

You can now specify whether IConfiguration key strings should be normalized to lower case or not when they are being converted into HOCON keys. You can read the documentation here

[1.5.12] / 3 August 2023

[1.5.8.1] / 12 July 2023

[1.5.8] / 21 June 2023

[1.5.7] / 23 May 2023

[1.5.6.1] / 17 May 2023

[1.5.6] / 10 May 2023

[1.5.5] / 4 May 2023

[1.5.4.1] / 1 May 2023

[1.5.4] / 24 April 2023

[1.5.3] / 24 April 2023

SQL Transaction Isolation Level Setting

In 1.5.3, we're introducing fine-grained control over transaction isolation level inside the Akka.Persistence.Hosting, Akka.Persistence.SqlServer.Hosting, and Akka.Persistence.PostgreSql.Hosting plugins.

you can go to the official Microsoft documentation to read more about these isolation level settings.

[1.5.2] / 6 April 2023

Major Changes

  • Persistence.Hosting default value for default serializer has been changed from json to null. This only affects persistence write and not reads. All objects with no serializer mapping will now be serialized using Akka default object serializer. If you have old persistence data where they do not have their serializer ID column populated, you will need to change this setting.

Inherited Changes From Akka.NET Core

  • Persistence will now ignore the serializer setting inside journal settings when writing new events. This setting will only be used when data retrieved from the database does not have the serializer id column unpopulated.
  • Cluster.Hosting, by default, will have SplitBrainResolver enabled.

[1.5.1.1] / 4 April 2023

[1.5.1] / 16 March 2023

[1.5.0] / 2 March 2023

Version 1.5.0 is the RTM release of Akka.Hosting and Akka.NET v1.5.0 RTM integration.

Full changes

Upgrading From v1.4 To v1.5

As noted in the upgrade advisories, there was some major changes inside Akka.NET that directly affects Akka.Hosting. To upgrade from v1.4 to v1.5, please watch our video here covering this process.