Bump Akka.Cluster.Hosting and Akka.Cluster.Sharding #323
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=80&v=4){kind=small}
Bumps Akka.Cluster.Hosting from 1.5.45 to 1.5.52 Bumps Akka.Cluster.Sharding from 1.5.49 to 1.5.52 --- updated-dependencies: - dependency-name: Akka.Cluster.Hosting dependency-version: 1.5.52 dependency-type: direct:production update-type: version-update:semver-patch - dependency-name: Akka.Cluster.Sharding dependency-version: 1.5.52 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
.NET
This was referenced Oct 10, 2025
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Updated Akka.Cluster.Hosting from 1.5.45 to 1.5.52.
Release notes
Sourced from Akka.Cluster.Hosting's releases.
1.5.52
1.5.52 October 9th 2025
API Changes
JournalOptions.Adaptersproperty. Users should migrate to the unified callback pattern:builder.WithJournal(options, journal => journal.AddWriteEventAdapter<T>(...)). The deprecated property will be removed in v1.6.0.Updates
1.5.51.1
1.5.51.1 October 2nd 2025
Bug Fixes
.WithHealthCheck()without adding event adapters1.5.51 October 1st 2025
New Features
WithHealthCheck<T>()generic methods for DI-resolved health checksUpdates
1.5.51
1.5.51 October 1st 2025
New Features
WithHealthCheck<T>()generic methods for DI-resolved health checksUpdates
1.5.50
1.5.50 September 23rd 2025
1.5.49
1.5.49 September 15th 2025
1.5.48.1
1.5.48.1 September 2nd 2025
Introduces new health check functionality and completey replaces Akka.HealthChecks
Problems with Akka.HealthChecks
There are a few major problems with Akka.HealthChecks:
How This Feature Solves Them
HealthCheckService.HealthCheckService- if you call any of theWithHealthCheckoverloads on theAkkaConfigurationBuilder, those types will automatically be registered with theMicrosoft.Extensions.Diagnostics.HealthChecks.HealthCheckServiceand they will "just work." No additional API calls required - happens automatically.ActorSystemliveness check - if it's dead, the check fails. And an Akka.Cluster "have we joined the cluster yet?" readiness check.These are not enabled by default - you have to opt-in to turning them on.
You can see what the outputs of this look like by running:
This will expose the output of both of these healthchecks as pretty-printed JSON at http://localhost:5000/healthz
{ "status": "Healthy", "totalDuration": "00:00:00.0002317", "checks": [ { "name": "ActorSystem Available", "status": "Healthy", "duration": "00:00:00.0000138", "description": "ActorSystem is running.", "tags": [ "akka" ], "data": {} }, { "name": "cluster.join", "status": "Healthy", "duration": "00:00:00.0000248", "description": "Successfully joined Akka.NET cluster after [0:00:06.3427821].", "tags": [ "ready", ... (truncated) ## 1.5.48 #### 1.5.48 August 22nd 2025 #### This release does not include the new healthcheck feature introduced in Akka.Hosting 1.5.47-beta1. * [Bump AkkaVersion from 1.5.46 to 1.5.48](https://github.com/akkadotnet/akka.net/releases/tag/1.5.48) * [Fix IndexOutOfRangeException bug in ConfigurationHoconAdapter](https://github.com/akkadotnet/Akka.Hosting/pull/632) * [Fix Akka.Hosting.TestKit deadlock on parallel unit test execution](https://github.com/akkadotnet/Akka.Hosting/pull/643) ## 1.5.47-beta1 #### 1.5.47-beta1 July 24th 2025 #### Introduces new health check functionality and completey replaces [Akka.HealthChecks](https://github.com/petabridge/akkadotnet-healthcheck) ### Problems with Akka.HealthChecks There are a few major problems with Akka.HealthChecks: 1. **Hair triggers that can inadvertently nuke an otherwise functioning Akka.NET cluster**: see https://github.com/petabridge/akkadotnet-healthcheck/issues/278 and https://github.com/petabridge/akkadotnet-healthcheck/issues/237 - we have had to do constant firefighting to get these right over the years. The fundamental problem is that Akka.HealthChecks tries to do too much and doesn't give the underlying systems time to recover, resulting in wild swings in availability. The new design approaches these things much more carefully and, generally, tries to use fewer, more meaningful health checks. 2. **Clunky and awkward to configure** - you have to configure health checks in three places, you have to install several different NuGet packages, and there are a lot of settings + moving parts involved. A lot of this is legacy baggage from before Microsoft.Extensions.Diagnostics.HealthChecks existed. 3. **Difficult to customize** - writing custom health checks with Akka.HealthCheck is... arduous, to say the least. ### How This Feature Solves Them 1. **No additional packages** - Akka.Hosting now takes a direct dependency on Microsoft.Extensions.Diagnostics.HealthChecks and exposes APIs for configuring Akka.NET-specific health checks that will be registered with the `HealthCheckService`. 2. **Automatic registration of health checks with `HealthCheckService`** - if you call any of the `WithHealthCheck` overloads on the `AkkaConfigurationBuilder`, those types will automatically be registered with the `Microsoft.Extensions.Diagnostics.HealthChecks.HealthCheckService` and they will "just work." No additional API calls required - happens automatically. 3. **Automatic health checks for core Akka and Akka.Cluster** - we ship with two built in checks out of the box: an `ActorSystem` liveness check - if it's dead, the check fails. And an Akka.Cluster "have we joined the cluster yet?" readiness check. **These are not enabled by default - you have to opt-in to turning them on.** You can see what the outputs of this look like by running: ```shell dotnet run --project src/Examples/Akka.Hosting.Asp.LoggingDemo/Akka.Hosting.Asp.LoggingDemo.csprojThis will expose the output of both of these healthchecks as pretty-printed JSON at http://localhost:5000/healthz
{ "status": "Healthy", "totalDuration": "00:00:00.0002317", "checks": [ { "name": "ActorSystem Available", "status": "Healthy", "duration": "00:00:00.0000138", "description": "ActorSystem is running.", "tags": [ "akka" ], "data": {} }, { "name": "cluster.join", "status": "Healthy", "duration": "00:00:00.0000248", "description": "Successfully joined Akka.NET cluster after [0:00:06.3427821].", "tags": [ "ready", ... (truncated) ## 1.5.46 #### 1.5.46 July 17th 2025 #### * [Bump AkkaVersion from 1.5.45 to 1.5.46](https://github.com/akkadotnet/akka.net/releases/tag/1.5.46) Commits viewable in [compare view](https://github.com/akkadotnet/Akka.Hosting/compare/1.5.45...1.5.52). </details> Updated [Akka.Cluster.Sharding](https://github.com/akkadotnet/akka.net) from 1.5.49 to 1.5.52. <details> <summary>Release notes</summary> _Sourced from [Akka.Cluster.Sharding's releases](https://github.com/akkadotnet/akka.net/releases)._ ## 1.5.52 #### 1.5.52 October 6th, 2025 #### **SECURITY PATCH** Akka.NET v1.5.52 is a security patch containing crucial fixes for enforcing certificate-based authentication using mTLS enforcement. Please see https://getakka.net/articles/remoting/security.html for details on how this works. * [Akka.Remote: implement mutual TLS authentication support](https://github.com/akkadotnet/akka.net/pull/7851) * [Akka.Remote: validate SSL certificate private key access at server startup](https://github.com/akkadotnet/akka.net/pull/7847) Other fixes: * [Akka.Cluster.Sharding: ShardedDaemonSets: randomize starting worker index](https://github.com/akkadotnet/akka.net/pull/7857) 1 contributors since release 1.5.51 | COMMITS | LOC+ | LOC- | AUTHOR | | --- | --- | --- | --- | | 3 | 1193 | 149 | Aaron Stannard | To [see the full set of changes in Akka.NET v1.5.52, click here](https://github.com/akkadotnet/akka.net/milestone/135?closed=1) ## Changes: * b4fbd5ffd00688e250126e0e004b95e2678532b0 added v1.5.52 release notes (#7883) * 5f8e39da189c1044aa0d9a5422c1421ea47603d0 `ShardedDaemonSets`: randomize starting worker index (#7857) (#7874) * 1a5a82bc5ce463f5a94cba7c943b28dd2b0a1fd9 feat(remote): implement mutual TLS authentication support (#7851) (#7855) [ #538 ] * 5994efc01eec66ec53b6bcd9a4fa2efb16b19043 Fix: Validate SSL certificate private key access at server startup (#7847) (#7848) [ #538 ] This list of changes was [auto generated](https://dev.azure.com/dotnet/Akka.NET/_build/results?buildId=120108&view=logs). ## 1.5.51 #### 1.5.51 October 1st, 2025 #### Akka.NET v1.5.51 is a minor patch containing a remoting bug fix and add required codes to support persistence health check. * [Remote: Fix DotNetty TLS handshake error handling](https://github.com/akkadotnet/akka.net/pull/7839) * [Persistence: Add health check handling code](https://github.com/akkadotnet/akka.net/pull/7842) 2 contributors since release 1.5.50 | COMMITS | LOC+ | LOC- | AUTHOR | |---------|------|------|---------------------| | 1 | 609 | 31 | Aaron Stannard | | 1 | 139 | 5 | Gregorius Soedharmo | To [see the full set of changes in Akka.NET v1.5.51, click here](https://github.com/akkadotnet/akka.net/milestone/134?closed=1) ## Changes: * 68dbe754043544ffe1242fb36826224e46b658a2 Update RELEASE_NOTES.md for 1.5.51 release (#7844) * ba5e5f89774102cb0f321e5a75138057e5a1fd44 Akka.Persistence HealthChecks (#7842) * 1ec6f9edfcb92da1c65f2ba67f2234c1e6274a8d Fix TLS handshake error handling (#7839) This list of changes was [auto generated](https://dev.azure.com/dotnet/Akka.NET/_build/results?buildId=119840&view=logs). ## 1.5.50 #### 1.5.50 September 22nd, 2025 #### Akka.NET v1.5.50 is a minor patch containing a bug fix. * [Remote: Propagate error from DotNetty TLS Handshake failure to Akka.Remote](https://github.com/akkadotnet/akka.net/pull/7824) 1 contributor since release 1.5.49 | COMMITS | LOC+ | LOC- | AUTHOR | |---------|------|------|---------------------| | 1 | 187 | 1 | Gregorius Soedharmo | To [see the full set of changes in Akka.NET v1.5.50, click here](https://github.com/akkadotnet/akka.net/milestone/133?closed=1) ## Changes: * 94124ba01b0c635b3908d2cdb789c3d0ac7e5ca9 Update RELEASE_NOTES.md for 1.5.50 release (#7837) * f595a8442cf6852752dced6e74d45826264a4bb3 Propagate error from DotNetty TLS handshake failure to Akka.Remote (#7824) This list of changes was [auto generated](https://dev.azure.com/dotnet/Akka.NET/_build/results?buildId=119695&view=logs). Commits viewable in [compare view](https://github.com/akkadotnet/akka.net/compare/1.5.49...1.5.52). </details> 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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) </details>