Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump AkkaHostingVersion from 1.5.20 to 1.5.25 #409

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jun 18, 2024

Bumps AkkaHostingVersion from 1.5.20 to 1.5.25.
Updates Akka.Persistence.Hosting from 1.5.20 to 1.5.25

Release notes

Sourced from Akka.Persistence.Hosting's releases.

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.24Add 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.22Add 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 =>
           {
               loggerConfigBuilder.WithLogFilter(filterBuilder =>
               {
                   filterBuilder.ExcludeMessageContaining("Test")%3B
               })
           }
   })
  1. Setting the loggerConfigBuilder.LogFilterBuilder property directly.

... (truncated)

Changelog

Sourced from Akka.Persistence.Hosting's changelog.

[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");

... (truncated)

Commits

Updates Akka.Cluster.Hosting from 1.5.20 to 1.5.25

Release notes

Sourced from Akka.Cluster.Hosting's releases.

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.24Add 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.22Add 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 =>
           {
               loggerConfigBuilder.WithLogFilter(filterBuilder =>
               {
                   filterBuilder.ExcludeMessageContaining("Test")%3B
               })
           }
   })
  1. Setting the loggerConfigBuilder.LogFilterBuilder property directly.

... (truncated)

Changelog

Sourced from Akka.Cluster.Hosting's changelog.

[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");

... (truncated)

Commits

Updates Akka.Cluster.Sharding from 1.5.20 to 1.5.25

Release notes

Sourced from Akka.Cluster.Sharding's releases.

Akka.NET v1.5.25

1.5.25 June 14th 2024

Akka.NET v1.5.25 includes a critical bug fix for logging and some other minor fixes.

Logging Errors Introduced in v1.5.21

Versions [v1.5.21,v1.5.24] are all affected by Akka.Logging: v1.5.21 appears to have truncated log source, timestamps, etc from all log messages - this was a bug introduced when we added the log-filtering feature we shipped in Akka.NET v1.5.21.

This issue has been resolved in v1.5.25 and we've added regression tests to ensure that the log format gets version-checked just like our APIs going forward.

Other fixes:

You can see the full set of changes for Akka.NET v1.5.25 here.

COMMITS LOC+ LOC- AUTHOR
6 347 44 Aaron Stannard
2 1197 1015 Gregorius Soedharmo

Changes:

  • 31222aa55740e3fdf170715b4d0a6d94c42b0cb4 added v1.5.25 release notes (#7257)
  • be4ed4dec28a386c60977923321adcb0fc8234cf Akka.Event: restore missing log data (#7256) [ #7255 ]
  • 6bcab70b87e2cac6de233cda4966569cce7fc8aa Akka.Router: automatically unpack IScheduledTellMsg when being handled through a router (#7249) [ #7247 ]
  • 487218c487304580a2e2468124d6c00a2bfe939e Modernize Cluster.Client code (#7251)
  • 260aee9ac209180a9adac8e3eb224155245dd9f0 add more appropriate settings for Ask vs. Tell benchmarking in BDN (#7248)
  • a14bb8447b88c7caa20842b1b673197278fb2842 Fix Akka.Discovery ServiceDiscovery instantiation (#7245)
  • 3bd219e69f7871cefbd458e50288b848e0c957b4 [Benchmarks] Add Ask vs. Tell memory pressure baseline (#7244)
  • b5a133a25f78ac082b81caf95a682f0516471dac RemotePingPong: don't let permission issues crash benchmark (#7241)
  • 12619cb220ab113f31beaa3db0120e536c87d930 Added v1.5.25 (#7240)

This list of changes was auto generated.

Akka.NET v1.5.24

1.5.24 June 7th 2024

Akka.NET v1.5.24 is a patch release for Akka.NET that addresses CVE-2018-8292 and also adds a quality of life improvement to IActorRef serialization.

COMMITS LOC+ LOC- AUTHOR
3 35 22 Gregorius Soedharmo
1 26 51 Mike Perrin

... (truncated)

Changelog

Sourced from Akka.Cluster.Sharding's changelog.

1.5.25 June 14th 2024

Akka.NET v1.5.25 includes a critical bug fix for logging and some other minor fixes.

Logging Errors Introduced in v1.5.21

Versions [v1.5.21,v1.5.24] are all affected by Akka.Logging: v1.5.21 appears to have truncated log source, timestamps, etc from all log messages - this was a bug introduced when we added the log-filtering feature we shipped in Akka.NET v1.5.21.

This issue has been resolved in v1.5.25 and we've added regression tests to ensure that the log format gets version-checked just like our APIs going forward.

Other fixes:

You can see the full set of changes for Akka.NET v1.5.25 here.

COMMITS LOC+ LOC- AUTHOR
6 347 44 Aaron Stannard
2 1197 1015 Gregorius Soedharmo

1.5.24 June 7th 2024

Akka.NET v1.5.24 is a patch release for Akka.NET that addresses CVE-2018-8292 and also adds a quality of life improvement to IActorRef serialization.

COMMITS LOC+ LOC- AUTHOR
3 35 22 Gregorius Soedharmo
1 26 51 Mike Perrin
1 15 2 Aaron Stannard

You can see the full set of changes for Akka.NET v1.5.24 here.

1.5.23 June 4th 2024

COMMITS LOC+ LOC- AUTHOR
2 299 44 Aaron Stannard
1 47 49 Gregorius Soedharmo
1 1 1 Hassan Abu Bakar

You can see the full set of changes for Akka.NET v1.5.23 here.

... (truncated)

Commits
  • 31222aa added v1.5.25 release notes (#7257)
  • be4ed4d Akka.Event: restore missing log data (#7256)
  • 6bcab70 Akka.Router: automatically unpack IScheduledTellMsg when being handled thro...
  • 487218c Modernize Cluster.Client code (#7251)
  • 260aee9 add more appropriate settings for Ask vs. Tell benchmarking in BDN (#7248)
  • a14bb84 Fix Akka.Discovery ServiceDiscovery instantiation (#7245)
  • 3bd219e [Benchmarks] Add Ask vs. Tell memory pressure baseline (#7244)
  • b5a133a RemotePingPong: don't let permission issues crash benchmark (#7241)
  • 12619cb Added v1.5.25 (#7240)
  • 0522779 Update RELEASE_NOTES.md for 1.5.24 release (#7239)
  • 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 <dependency name> 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)

Bumps `AkkaHostingVersion` from 1.5.20 to 1.5.25.

Updates `Akka.Persistence.Hosting` from 1.5.20 to 1.5.25
- [Release notes](https://github.com/akkadotnet/Akka.Hosting/releases)
- [Changelog](https://github.com/akkadotnet/Akka.Hosting/blob/dev/RELEASE_NOTES.md)
- [Commits](akkadotnet/Akka.Hosting@1.5.20...1.5.25)

Updates `Akka.Cluster.Hosting` from 1.5.20 to 1.5.25
- [Release notes](https://github.com/akkadotnet/Akka.Hosting/releases)
- [Changelog](https://github.com/akkadotnet/Akka.Hosting/blob/dev/RELEASE_NOTES.md)
- [Commits](akkadotnet/Akka.Hosting@1.5.20...1.5.25)

Updates `Akka.Cluster.Sharding` from 1.5.20 to 1.5.25
- [Release notes](https://github.com/akkadotnet/akka.net/releases)
- [Changelog](https://github.com/akkadotnet/akka.net/blob/dev/RELEASE_NOTES.md)
- [Commits](akkadotnet/akka.net@1.5.20...1.5.25)

---
updated-dependencies:
- dependency-name: Akka.Persistence.Hosting
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: Akka.Cluster.Hosting
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: Akka.Cluster.Sharding
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Jun 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants