search

akkadotnet / Akka.Persistence.SqlServer

Akka.Persistence.SqlServer provider
Apache License 2.0
59 stars 49 forks source link

Bump AkkaHostingVersion from 1.5.15 to 1.5.27 #392

Closed dependabot[bot] closed 1 month ago

dependabot[bot] commented 1 month ago

Bumps AkkaHostingVersion from 1.5.15 to 1.5.27. Updates Akka.Hosting from 1.5.15 to 1.5.27

Release notes

Sourced from Akka.Hosting's releases.

Akka.Hosting 1.5.27

• Update Akka.NET to 1.5.27.1 • Fix only the last ShardOptions were applied • Add ClusterClientDiscovery support

[!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.

Akka.Hosting 1.5.25

• Update Akka.NET to 1.5.25%2C which resolves a critical bug: Akka.Logging: v1.5.21 appears to have truncated log source%2C timestamps%2C etc from all log messages

Akka.Hosting v1.5.24

• Update Akka.NET to 1.5.24 • Add ShardedDaemonProcess integration 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)

Akka.Hosting v1.5.22

• Update Akka.NET to 1.5.22 • Add log filtering extension method Filtering Logs In Akka.NET In Akka.NET 1.5.21%2C we introduced log filtering for log messages based on the LogSource or the content of a log message. Depending on your coding style%2C 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"%2C configurationBuilder =>
   {
       configurationBuilder
           .ConfigureLoggers(loggerConfigBuilder =>
           {
</tr></table>

... (truncated)

Changelog

Sourced from Akka.Hosting's changelog.

[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.

... (truncated)

Commits
  • 0ba7118 Update RELEASE_NOTES.md for 1.5.27 release (#481)
  • 3ec5de4 Add ClusterClientDiscovery Hosting extension support (#478)
  • 2e56b9f Fix how ClusterShardingSettings were applied (#480)
  • 57c65bc Bump AkkaVersion from 1.5.26 to 1.5.27.1 (#479)
  • 129d59f Bump AkkaVersion from 1.5.25 to 1.5.26 (#471)
  • 23b08a5 Bump Akka.Logger.Serilog from 1.5.12.1 to 1.5.25 (#469)
  • 0b4103f Added v1.5.25 release notes (#468)
  • fc04d86 Upgrade to Akka.NET v1.5.25 (#467)
  • ee4b518 Bump Serilog.Sinks.Console from 5.0.1 to 6.0.0 (#464)
  • 923bc7f Update RELEASE_NOTES.md for 1.5.24 release (#465)
  • Additional commits viewable in compare view


Updates Akka.Persistence.Hosting from 1.5.15 to 1.5.27

Release notes

Sourced from Akka.Persistence.Hosting's releases.

Akka.Hosting 1.5.27

• Update Akka.NET to 1.5.27.1 • Fix only the last ShardOptions were applied • Add ClusterClientDiscovery support

[!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.

Akka.Hosting 1.5.25

• Update Akka.NET to 1.5.25%2C which resolves a critical bug: Akka.Logging: v1.5.21 appears to have truncated log source%2C timestamps%2C etc from all log messages

Akka.Hosting v1.5.24

• Update Akka.NET to 1.5.24 • Add ShardedDaemonProcess integration 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)

Akka.Hosting v1.5.22

• Update Akka.NET to 1.5.22 • Add log filtering extension method Filtering Logs In Akka.NET In Akka.NET 1.5.21%2C we introduced log filtering for log messages based on the LogSource or the content of a log message. Depending on your coding style%2C 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"%2C configurationBuilder =>
   {
       configurationBuilder
           .ConfigureLoggers(loggerConfigBuilder =>
           {
</tr></table>

... (truncated)

Changelog

Sourced from Akka.Persistence.Hosting's changelog.

[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.

... (truncated)

Commits
  • 0ba7118 Update RELEASE_NOTES.md for 1.5.27 release (#481)
  • 3ec5de4 Add ClusterClientDiscovery Hosting extension support (#478)
  • 2e56b9f Fix how ClusterShardingSettings were applied (#480)
  • 57c65bc Bump AkkaVersion from 1.5.26 to 1.5.27.1 (#479)
  • 129d59f Bump AkkaVersion from 1.5.25 to 1.5.26 (#471)
  • 23b08a5 Bump Akka.Logger.Serilog from 1.5.12.1 to 1.5.25 (#469)
  • 0b4103f Added v1.5.25 release notes (#468)
  • fc04d86 Upgrade to Akka.NET v1.5.25 (#467)
  • ee4b518 Bump Serilog.Sinks.Console from 5.0.1 to 6.0.0 (#464)
  • 923bc7f Update RELEASE_NOTES.md for 1.5.24 release (#465)
  • Additional commits viewable in compare view


Updates Akka.Cluster.Hosting from 1.5.15 to 1.5.27

Release notes

Sourced from Akka.Cluster.Hosting's releases.

Akka.Hosting 1.5.27

• Update Akka.NET to 1.5.27.1 • Fix only the last ShardOptions were applied • Add ClusterClientDiscovery support

[!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.

Akka.Hosting 1.5.25

• Update Akka.NET to 1.5.25%2C which resolves a critical bug: Akka.Logging: v1.5.21 appears to have truncated log source%2C timestamps%2C etc from all log messages

Akka.Hosting v1.5.24

• Update Akka.NET to 1.5.24 • Add ShardedDaemonProcess integration 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)

Akka.Hosting v1.5.22

• Update Akka.NET to 1.5.22 • Add log filtering extension method Filtering Logs In Akka.NET In Akka.NET 1.5.21%2C we introduced log filtering for log messages based on the LogSource or the content of a log message. Depending on your coding style%2C 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"%2C configurationBuilder =>
   {
       configurationBuilder
           .ConfigureLoggers(loggerConfigBuilder =>
           {
</tr></table>

... (truncated)

Changelog

Sourced from Akka.Cluster.Hosting's changelog.

[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.

... (truncated)

Commits
  • 0ba7118 Update RELEASE_NOTES.md for 1.5.27 release (#481)
  • 3ec5de4 Add ClusterClientDiscovery Hosting extension support (#478)
  • 2e56b9f Fix how ClusterShardingSettings were applied (#480)
  • 57c65bc Bump AkkaVersion from 1.5.26 to 1.5.27.1 (#479)
  • 129d59f Bump AkkaVersion from 1.5.25 to 1.5.26 (#471)
  • 23b08a5 Bump Akka.Logger.Serilog from 1.5.12.1 to 1.5.25 (#469)
  • 0b4103f Added v1.5.25 release notes (#468)
  • fc04d86 Upgrade to Akka.NET v1.5.25 (#467)
  • ee4b518 Bump Serilog.Sinks.Console from 5.0.1 to 6.0.0 (#464)
  • 923bc7f Update RELEASE_NOTES.md for 1.5.24 release (#465)
  • Additional 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 rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)