Skip to content

Bump Akka.Hosting from 1.5.8 to 1.5.68#2

Open
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/nuget/src/Akka.Hosting-1.5.68
Open

Bump Akka.Hosting from 1.5.8 to 1.5.68#2
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/nuget/src/Akka.Hosting-1.5.68

Conversation

@dependabot
Copy link
Copy Markdown

@dependabot dependabot Bot commented on behalf of github May 21, 2026

Updated Akka.Hosting from 1.5.8 to 1.5.68.

Release notes

Sourced from Akka.Hosting's releases.

1.5.68

1.5.68 May 18th 2026

Security Fixes

  • Resolve GHSA-g94r-2vxg-569j by bumping OpenTelemetry minimum to 1.10.0 - OpenTelemetry.Api 1.9.0 has a known moderate severity vulnerability. The minimum OpenTelemetry version floor has been raised from 1.9.0 to 1.10.0, and the Microsoft.Extensions.Logging floor has been raised to 9.0.0. Downstream consumers that previously resolved to the vulnerable OpenTelemetry.Api 1.9.0 will now pull the safe 1.10.0 release.

Bug Fixes

  • Fix implicit-sender leak under xUnit v3 parallel execution in Akka.Hosting.TestKit - Under xUnit v3's default parallel-class scheduling, await continuations could resume on ThreadPool threads where a sibling test had pinned its actor cell, causing Tell() to use the wrong implicit sender and replies to land in the wrong TestActor's mailbox. A new wrapping SynchronizationContext preserves xUnit's scheduler while pinning the ambient actor cell across await continuations.
  • Fix SynchronizationContext leak and TestActor startup race in Akka.Hosting.TestKit - Two compounding sources of flakiness in sequential xUnit v3 suites: (1) the ActorCellKeepingSynchronizationContext installed during host startup leaked out of the initialization callback and was inherited by subsequent tests, pinning continuations onto disposed ActorCells; (2) the TestActor created during host startup was intermittently terminated by a race with other /system actors starting concurrently. Fixed by bracketing the context installation with a save/restore and adding post-startup TestActor liveness verification with automatic re-creation.
  • Fix cached TestProbe refs becoming stale after TestActor recovery in Akka.Hosting.TestKit - Actors created during WithActors could cache IRequiredActor<TestProbe>.ActorRef before recovery ran. Re-registering a new raw TestActor in ActorRegistry did not update those cached refs. TestProbe is now registered via a stable forwarding actor whose target is swapped atomically after recovery, ensuring all cached references remain valid.

1.5.67

1.5.67 April 26th 2026

New Features

  • Add WithStrictSerialization helperresolves issue #​734. Adds WithStrictSerialization(bool enabled = true) extension on AkkaConfigurationBuilder that sets akka.actor.serialization-settings.allow-unregistered-types = off, disabling the Newtonsoft.Json fallback and throwing SerializationException for unregistered types.

Updates

1.5.65

1.5.65 April 10th 2026

Updates

1.5.64

1.5.64 March 31st 2026

Bug Fixes

  • Fix LoggerFactoryLogger metadata regression for non-semantic logs - PR #​706 (trace correlation) accidentally gated ActorPath, LogSource, Timestamp, and Thread emission on _hasSemanticProperties, which was false for plain-string logs. Non-semantic logs lost all structured metadata, breaking downstream consumers such as Datadog pipelines and custom ConsoleFormatters. All log paths now emit the full set of Akka metadata as structured attributes regardless of whether the message uses named placeholders.

Breaking Changes

  • Convert Akka.Hosting.TestKit to xUnit 3 - Akka.Hosting.TestKit now targets xUnit v3. Users who need to remain on xUnit v2 can switch to the new Akka.Hosting.TestKit.Xunit2 package, which preserves the previous xUnit v2-based TestKit API.

Updates

1.5.63

1.5.63 March 24th 2026

Bug Fixes

Updates

1.5.62

1.5.62 March 4th 2026

Updates

1.5.61 February 26th 2026

Updates

1.5.60 February 10th 2026

New Features

  • Add OpenTelemetry trace correlation support for LoggerFactoryLogger - enables proper trace correlation for logs emitted from actor code. Solves the problem that Activity.Current doesn't flow across actor mailbox boundaries because it uses AsyncLocal<T>. When using Akka.NET 1.5.59+, LogEvent.ActivityContext captures trace context at log creation time and flows it through to OpenTelemetry LogRecords via the new AkkaTraceContextProcessor. Register with options.AddAkkaTraceCorrelation() in your OpenTelemetry logging configuration.
  • Add WithContext() integration tests for MEL logger - confirmed that Akka.NET 1.5.60's WithContext() logging context enrichment works automatically with LoggerFactoryLogger. Context properties set via the core WithContext() API flow through to Microsoft.Extensions.Logging state dictionaries via TryGetProperties() without any code changes needed.

Bug Fixes

Deprecations

  • WithDefaultLogMessageFormatter<T>() is now marked [Obsolete]SemanticLogMessageFormatter is the default as of Akka.NET 1.5.58 and no longer needs to be set explicitly. The method still works for custom ILogMessageFormatter implementations.

Updates

1.5.60-beta1 January 29th 2026

Beta Release

This is a beta release for testing the OpenTelemetry trace correlation feature that was merged after 1.5.59.

New Features

  • Add OpenTelemetry trace correlation support for LoggerFactoryLogger - enables proper trace correlation for logs emitted from actor code. Solves the problem that Activity.Current doesn't flow across actor mailbox boundaries because it uses AsyncLocal<T>. When using Akka.NET 1.5.59+, LogEvent.ActivityContext captures trace context at log creation time and flows it through to OpenTelemetry LogRecords via the new AkkaTraceContextProcessor. Register with options.AddAkkaTraceCorrelation() in your OpenTelemetry logging configuration.

1.5.59 January 2026

New Features

  • Add OpenTelemetry trace correlation support for LoggerFactoryLogger - enables proper trace correlation for logs emitted from actor code. Solves the problem that Activity.Current doesn't flow across actor mailbox boundaries because it uses AsyncLocal<T>. When using Akka.NET 1.5.59+, LogEvent.ActivityContext captures trace context at log creation time and flows it through to OpenTelemetry LogRecords via the new AkkaTraceContextProcessor. Register with options.AddAkkaTraceCorrelation() in your OpenTelemetry logging configuration.

Bug Fixes

Updates

1.5.58 January 9th 2026

Updates
... (truncated)

1.5.61

1.5.61 February 26th 2026

Updates

1.5.60 February 10th 2026

New Features

  • Add OpenTelemetry trace correlation support for LoggerFactoryLogger - enables proper trace correlation for logs emitted from actor code. Solves the problem that Activity.Current doesn't flow across actor mailbox boundaries because it uses AsyncLocal<T>. When using Akka.NET 1.5.59+, LogEvent.ActivityContext captures trace context at log creation time and flows it through to OpenTelemetry LogRecords via the new AkkaTraceContextProcessor. Register with options.AddAkkaTraceCorrelation() in your OpenTelemetry logging configuration.
  • Add WithContext() integration tests for MEL logger - confirmed that Akka.NET 1.5.60's WithContext() logging context enrichment works automatically with LoggerFactoryLogger. Context properties set via the core WithContext() API flow through to Microsoft.Extensions.Logging state dictionaries via TryGetProperties() without any code changes needed.

Bug Fixes

Deprecations

  • WithDefaultLogMessageFormatter<T>() is now marked [Obsolete]SemanticLogMessageFormatter is the default as of Akka.NET 1.5.58 and no longer needs to be set explicitly. The method still works for custom ILogMessageFormatter implementations.

Updates

1.5.60-beta1 January 29th 2026

Beta Release

This is a beta release for testing the OpenTelemetry trace correlation feature that was merged after 1.5.59.

New Features

  • Add OpenTelemetry trace correlation support for LoggerFactoryLogger - enables proper trace correlation for logs emitted from actor code. Solves the problem that Activity.Current doesn't flow across actor mailbox boundaries because it uses AsyncLocal<T>. When using Akka.NET 1.5.59+, LogEvent.ActivityContext captures trace context at log creation time and flows it through to OpenTelemetry LogRecords via the new AkkaTraceContextProcessor. Register with options.AddAkkaTraceCorrelation() in your OpenTelemetry logging configuration.

1.5.59 January 2026

New Features

  • Add OpenTelemetry trace correlation support for LoggerFactoryLogger - enables proper trace correlation for logs emitted from actor code. Solves the problem that Activity.Current doesn't flow across actor mailbox boundaries because it uses AsyncLocal<T>. When using Akka.NET 1.5.59+, LogEvent.ActivityContext captures trace context at log creation time and flows it through to OpenTelemetry LogRecords via the new AkkaTraceContextProcessor. Register with options.AddAkkaTraceCorrelation() in your OpenTelemetry logging configuration.

Bug Fixes

Updates

1.5.58 January 9th 2026

Updates

1.5.57 December 16th 2025

New Features
... (truncated)

1.5.60

1.5.60 February 10th 2026

New Features

  • Add OpenTelemetry trace correlation support for LoggerFactoryLogger - enables proper trace correlation for logs emitted from actor code. Solves the problem that Activity.Current doesn't flow across actor mailbox boundaries because it uses AsyncLocal<T>. When using Akka.NET 1.5.59+, LogEvent.ActivityContext captures trace context at log creation time and flows it through to OpenTelemetry LogRecords via the new AkkaTraceContextProcessor. Register with options.AddAkkaTraceCorrelation() in your OpenTelemetry logging configuration.
  • Add WithContext() integration tests for MEL logger - confirmed that Akka.NET 1.5.60's WithContext() logging context enrichment works automatically with LoggerFactoryLogger. Context properties set via the core WithContext() API flow through to Microsoft.Extensions.Logging state dictionaries via TryGetProperties() without any code changes needed.

Bug Fixes

Deprecations

  • WithDefaultLogMessageFormatter<T>() is now marked [Obsolete]SemanticLogMessageFormatter is the default as of Akka.NET 1.5.58 and no longer needs to be set explicitly. The method still works for custom ILogMessageFormatter implementations.

Updates

1.5.60-beta1 January 29th 2026

Beta Release

This is a beta release for testing the OpenTelemetry trace correlation feature that was merged after 1.5.59.

New Features

  • Add OpenTelemetry trace correlation support for LoggerFactoryLogger - enables proper trace correlation for logs emitted from actor code. Solves the problem that Activity.Current doesn't flow across actor mailbox boundaries because it uses AsyncLocal<T>. When using Akka.NET 1.5.59+, LogEvent.ActivityContext captures trace context at log creation time and flows it through to OpenTelemetry LogRecords via the new AkkaTraceContextProcessor. Register with options.AddAkkaTraceCorrelation() in your OpenTelemetry logging configuration.

1.5.59 January 2026

New Features

  • Add OpenTelemetry trace correlation support for LoggerFactoryLogger - enables proper trace correlation for logs emitted from actor code. Solves the problem that Activity.Current doesn't flow across actor mailbox boundaries because it uses AsyncLocal<T>. When using Akka.NET 1.5.59+, LogEvent.ActivityContext captures trace context at log creation time and flows it through to OpenTelemetry LogRecords via the new AkkaTraceContextProcessor. Register with options.AddAkkaTraceCorrelation() in your OpenTelemetry logging configuration.

Bug Fixes

Updates

1.5.58 January 9th 2026

Updates

1.5.57 December 16th 2025

New Features

  • Add semantic logging support for Akka.NET 1.5.56+ - enables Microsoft.Extensions.Logging to receive properly structured state dictionaries instead of pre-formatted strings. When using Akka.NET 1.5.56+, log messages now include structured properties from the semantic logging API along with Akka metadata (ActorPath, Timestamp, Thread, LogSource). Fully backwards compatible with older Akka.NET versions.

Updates

... (truncated)

1.5.60-beta1

1.5.60-beta1 January 29th 2026

Beta Release

This is a beta release for testing the OpenTelemetry trace correlation feature that was merged after 1.5.59.

New Features

  • Add OpenTelemetry trace correlation support for LoggerFactoryLogger - enables proper trace correlation for logs emitted from actor code. Solves the problem that Activity.Current doesn't flow across actor mailbox boundaries because it uses AsyncLocal<T>. When using Akka.NET 1.5.59+, LogEvent.ActivityContext captures trace context at log creation time and flows it through to OpenTelemetry LogRecords via the new AkkaTraceContextProcessor. Register with options.AddAkkaTraceCorrelation() in your OpenTelemetry logging configuration.

1.5.59

1.5.59 January 26th 2026

Bug Fixes

Updates

1.5.58 January 9th 2026

Updates

1.5.57 December 16th 2025

New Features

  • Add semantic logging support for Akka.NET 1.5.56+ - enables Microsoft.Extensions.Logging to receive properly structured state dictionaries instead of pre-formatted strings. When using Akka.NET 1.5.56+, log messages now include structured properties from the semantic logging API along with Akka metadata (ActorPath, Timestamp, Thread, LogSource). Fully backwards compatible with older Akka.NET versions.

Updates

1.5.55.1 October 27th 2025

Enhancements

  • Expose options in journal and snapshot builders - resolved issue #​690 by adding Options property to AkkaPersistenceJournalBuilder and AkkaPersistenceSnapshotBuilder. Extension methods can now access configuration details without requiring options as explicit parameters, eliminating redundant option passing for connectivity health checks and other plugin-specific features

1.5.55 October 26th 2025

New Features

Enhancements

Updates

1.5.55-beta1 October 26th 2025

New Features

Enhancements

Updates
... (truncated)

1.5.58

1.5.58 January 9th 2026

Updates

1.5.57 December 16th 2025

New Features

  • Add semantic logging support for Akka.NET 1.5.56+ - enables Microsoft.Extensions.Logging to receive properly structured state dictionaries instead of pre-formatted strings. When using Akka.NET 1.5.56+, log messages now include structured properties from the semantic logging API along with Akka metadata (ActorPath, Timestamp, Thread, LogSource). Fully backwards compatible with older Akka.NET versions.

Updates

1.5.55.1 October 27th 2025

Enhancements

  • Expose options in journal and snapshot builders - resolved issue #​690 by adding Options property to AkkaPersistenceJournalBuilder and AkkaPersistenceSnapshotBuilder. Extension methods can now access configuration details without requiring options as explicit parameters, eliminating redundant option passing for connectivity health checks and other plugin-specific features

1.5.55 October 26th 2025

New Features

Enhancements

Updates

1.5.55-beta1 October 26th 2025

New Features

Enhancements

Updates

1.5.53 October 14th 2025

Bug Fixes

  • Fix event adapter callback API not invoking adapters at runtime - resolved critical bug where event adapters configured via the callback API were not being invoked at runtime. This fix is especially important for users who have migrated to the callback pattern following the deprecation of JournalOptions.Adapters property. The issue was caused by unnecessary fallback configuration that interfered with adapter registration during HOCON merging.

Updates

1.5.57

1.5.57 December 16th 2025

New Features

  • Add semantic logging support for Akka.NET 1.5.56+ - enables Microsoft.Extensions.Logging to receive properly structured state dictionaries instead of pre-formatted strings. When using Akka.NET 1.5.56+, log messages now include structured properties from the semantic logging API along with Akka metadata (ActorPath, Timestamp, Thread, LogSource). Fully backwards compatible with older Akka.NET versions.

Updates

1.5.55.1 October 27th 2025

Enhancements

  • Expose options in journal and snapshot builders - resolved issue #​690 by adding Options property to AkkaPersistenceJournalBuilder and AkkaPersistenceSnapshotBuilder. Extension methods can now access configuration details without requiring options as explicit parameters, eliminating redundant option passing for connectivity health checks and other plugin-specific features

1.5.55 October 26th 2025

New Features

Enhancements

Updates

1.5.55-beta1 October 26th 2025

New Features

Enhancements

Updates

1.5.53 October 14th 2025

Bug Fixes

  • Fix event adapter callback API not invoking adapters at runtime - resolved critical bug where event adapters configured via the callback API were not being invoked at runtime. This fix is especially important for users who have migrated to the callback pattern following the deprecation of JournalOptions.Adapters property. The issue was caused by unnecessary fallback configuration that interfered with adapter registration during HOCON merging.

Updates

1.5.52 October 9th 2025

API Changes
... (truncated)

1.5.57-beta2

1.5.57-beta2 December 3rd 2025

New Features

  • Add semantic logging support for Akka.NET 1.5.56+ - enables Microsoft.Extensions.Logging to receive properly structured state dictionaries instead of pre-formatted strings. When using Akka.NET 1.5.56+, log messages now include structured properties from the semantic logging API along with Akka metadata (ActorPath, Timestamp, Thread, LogSource). Fully backwards compatible with older Akka.NET versions.

Updates

1.5.55.1 October 27th 2025

Enhancements

  • Expose options in journal and snapshot builders - resolved issue #​690 by adding Options property to AkkaPersistenceJournalBuilder and AkkaPersistenceSnapshotBuilder. Extension methods can now access configuration details without requiring options as explicit parameters, eliminating redundant option passing for connectivity health checks and other plugin-specific features

1.5.55 October 26th 2025

New Features

Enhancements

Updates

1.5.55-beta1 October 26th 2025

New Features

Enhancements

Updates

1.5.53 October 14th 2025

Bug Fixes

  • Fix event adapter callback API not invoking adapters at runtime - resolved critical bug where event adapters configured via the callback API were not being invoked at runtime. This fix is especially important for users who have migrated to the callback pattern following the deprecation of JournalOptions.Adapters property. The issue was caused by unnecessary fallback configuration that interfered with adapter registration during HOCON merging.

Updates

1.5.52 October 9th 2025

API Changes
... (truncated)

1.5.55.1

1.5.55.1 October 27th 2025

Enhancements

  • Expose options in journal and snapshot builders - resolved issue #​690 by adding Options property to AkkaPersistenceJournalBuilder and AkkaPersistenceSnapshotBuilder. Extension methods can now access configuration details without requiring options as explicit parameters, eliminating redundant option passing for connectivity health checks and other plugin-specific features

1.5.55 October 26th 2025

New Features

Enhancements

Updates

1.5.55-beta1 October 26th 2025

New Features

Enhancements

Updates

1.5.53 October 14th 2025

Bug Fixes

  • Fix event adapter callback API not invoking adapters at runtime - resolved critical bug where event adapters configured via the callback API were not being invoked at runtime. This fix is especially important for users who have migrated to the callback pattern following the deprecation of JournalOptions.Adapters property. The issue was caused by unnecessary fallback configuration that interfered with adapter registration during HOCON merging.

Updates

1.5.52 October 9th 2025

API Changes

Updates

1.5.51.1 October 2nd 2025

Bug Fixes
... (truncated)

1.5.55

1.5.55 October 26th 2025

New Features

Enhancements

Updates

1.5.55-beta1 October 26th 2025

New Features

Enhancements

Updates

1.5.53 October 14th 2025

Bug Fixes

  • Fix event adapter callback API not invoking adapters at runtime - resolved critical bug where event adapters configured via the callback API were not being invoked at runtime. This fix is especially important for users who have migrated to the callback pattern following the deprecation of JournalOptions.Adapters property. The issue was caused by unnecessary fallback configuration that interfered with adapter registration during HOCON merging.

Updates

1.5.52 October 9th 2025

API Changes

Updates

1.5.51.1 October 2nd 2025

Bug Fixes

1.5.51 October 1st 2025

New Features
... (truncated)

1.5.55-beta1

1.5.55-beta1 October 26th 2025

New Features

Enhancements

Updates

1.5.53

1.5.53 October 14th 2025

Bug Fixes

  • Fix event adapter callback API not invoking adapters at runtime - resolved critical bug where event adapters configured via the callback API were not being invoked at runtime. This fix is especially important for users who have migrated to the callback pattern following the deprecation of JournalOptions.Adapters property. The issue was caused by unnecessary fallback configuration that interfered with adapter registration during HOCON merging.

Updates

1.5.52 October 9th 2025

API Changes

Updates

1.5.51.1 October 2nd 2025

Bug Fixes

1.5.51 October 1st 2025

New Features

Updates

1.5.52

1.5.52 October 9th 2025

API Changes

Updates

1.5.51.1

1.5.51.1 October 2nd 2025

Bug Fixes

1.5.51 October 1st 2025

New Features

Updates

1.5.51

1.5.51 October 1st 2025

New Features

Updates

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:

  1. Hair triggers that can inadvertently nuke an otherwise functioning Akka.NET cluster: see Relaxing Akka.Persistence.HealthCheck petabridge/akkadotnet-healthcheck#278 and Rewrite Cluster health checks petabridge/akkadotnet-healthcheck#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:

dotnet run --project src/Examples/Akka.Hosting.Asp.LoggingDemo/Akka.Hosting.Asp.LoggingDemo.csproj

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

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


## 1.5.45

#### 1.5.45 July 7th 2025 ####

* [Bump AkkaVersion from 1.5.44 to 1.5.45](https://github.com/akkadotnet/akka.net/releases/tag/1.5.45)


## 1.5.44

#### 1.5.44 June 23rd 2025 ####

* [Bump AkkaVersion from 1.5.40 to 1.5.44](https://github.com/akkadotnet/akka.net/releases/tag/1.5.44)
* [Add persistence testkit support](https://github.com/akkadotnet/Akka.Hosting/pull/610)


## 1.5.42

#### 1.5.42 May 21st 2025 ####

* [Bump AkkaVersion from 1.5.40 to 1.5.42](https://github.com/akkadotnet/akka.net/releases/tag/1.5.42)
* [Fix `.WithDistributedData()` to start `DistributedDataProvider` automatically](https://github.com/akkadotnet/Akka.Hosting/pull/597)


## 1.5.40

#### 1.5.40 March 24th 2025 ####

* [Bump AkkaVersion from 1.5.39 to 1.5.40](https://github.com/akkadotnet/akka.net/releases/tag/1.5.40)


## 1.5.39

#### 1.5.39 March 17th 2025 ####

* [Bump AkkaVersion from 1.5.38 to 1.5.39](https://github.com/akkadotnet/akka.net/releases/tag/1.5.39)


## 1.5.38

#### 1.5.38 February 17th 2025 ####

* [Bump AkkaVersion from 1.5.37 to 1.5.38](https://github.com/akkadotnet/akka.net/releases/tag/1.5.38)


## 1.5.37.2

#### 1.5.37.2 February 5th 2024 ####

* [Akka.Hosting.TestKit: Fixed issue with `xUnitLogger` throwing `NotImplementedException` when used with scoped logging](https://github.com/akkadotnet/Akka.Hosting/pull/570).


## 1.5.37.1

#### 1.5.37 January 23rd 2025 ####

Moving all of our BCL dependencies to 8.0 created issues for our .NET 6-9 users when adopting Akka.NET packages that only targeted .NET Standard, so for the time being we're normalizing everything back to 6.0

* [Bump Akka.NET to 1.5.37](https://github.com/akkadotnet/akka.net/releases/tag/1.5.37)


## 1.5.37

#### 1.5.37 January 23rd 2025 ####

Moving all of our BCL dependencies to 8.0 created issues for our .NET 6-9 users when adopting Akka.NET packages that only targeted .NET Standard, so for the time being we're normalizing everything back to 6.0

* [Bump Akka.NET to 1.5.37](https://github.com/akkadotnet/akka.net/releases/tag/1.5.37)


## 1.5.36

#### 1.5.36 January 22nd 2025 ####

* [Bump Akka.NET to 1.5.36](https://github.com/akkadotnet/akka.net/releases/tag/1.5.36)


## 1.5.35

#### 1.5.35 January 13th 2025 ####

* [Bump Akka.NET to 1.5.35](https://github.com/akkadotnet/akka.net/releases/tag/1.5.35)
* [Bump Microsoft.Extensions.* packages to 8.0.X](https://github.com/akkadotnet/Akka.Hosting/pull/553)
* [Bump Microsoft.Bcl.AsyncInterfaces to 8.0.X](https://github.com/akkadotnet/Akka.Hosting/pull/553)
* [Bump System.Text.Json to 8.0.X](https://github.com/akkadotnet/Akka.Hosting/pull/553)


## 1.5.34

#### 1.5.34 January 7th 2025 ####

* [Bump Akka.NET to 1.5.34](https://github.com/akkadotnet/akka.net/releases/tag/1.5.34)


## 1.5.33

#### 1.5.33 December 24th 2024 ####

* [Bump Akka.NET to 1.5.33](https://github.com/akkadotnet/akka.net/releases/tag/1.5.33)
* Resolved `nullability` issues with Akka.Hosting.TestKit APIs

## 1.5.32

#### 1.5.32 December 4th 2024 ####

* [Bump Akka.NET to 1.5.32](https://github.com/akkadotnet/akka.net/releases/tag/1.5.32)
* [Cluster: Add global scoped DData setting extension method](https://github.com/akkadotnet/Akka.Hosting/pull/527)
* [Core: Fix CVE-2024-43485](https://github.com/akkadotnet/Akka.Hosting/pull/529)


## 1.5.31.1

#### 1.5.31.1 November 15th 2024 ####

* [Cluster: Fix `WithSingleton` and `WithSingletonProxy` API](https://github.com/akkadotnet/Akka.Hosting/pull/520)
* [Cluster: Fix `WithShardedDaemonProcess` throws `NullReferenceException`](https://github.com/akkadotnet/Akka.Hosting/pull/522)


## 1.5.31

#### 1.5.31 November 11th 2024 ####

* [Bump AkkaVersion from 1.5.30 to 1.5.31](https://github.com/akkadotnet/Akka.Hosting/pull/517)


## 1.5.30.1

• [Fix ActorRegistry.GetAsync() returning Nobody](https://github.com/akkadotnet/Akka.Hosting/pull/501)

## 1.5.30

• [Update Akka.NET to 1.5.30](https://github.com/akkadotnet/akka.net/releases/tag/1.5.30)
• [Make sure that any exceptions thrown during start-up are logged and stops the application](https://github.com/akkadotnet/Akka.Hosting/pull/494)

## 1.5.29

• [Update Akka.NET to 1.5.29](https://github.com/akkadotnet/akka.net/releases/tag/1.5.29)
• [Make sure that any exceptions thrown during start-up are logged and stops the application](https://github.com/akkadotnet/Akka.Hosting/pull/494)

## 1.5.28

• [Update Akka.NET to 1.5.28](https://github.com/akkadotnet/akka.net/releases/tag/1.5.29)
• [Include Akka.Streams configuration by default](https://github.com/akkadotnet/Akka.Hosting/pull/489)

## 1.5.27

• [Update Akka.NET to 1.5.27.1](https://github.com/akkadotnet/akka.net/releases/tag/1.5.27.1)
• [Fix only the last ShardOptions were applied](https://github.com/akkadotnet/Akka.Hosting/pull/480)
• [Add ClusterClientDiscovery support](https://github.com/akkadotnet/Akka.Hosting/pull/478)
> [!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

• [Update Akka.NET to 1.5.25](https://github.com/akkadotnet/akka.net/releases/tag/1.5.25)%2C which resolves a critical bug: [Akka.Logging: v1.5.21...

_Description has been truncated_

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

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added .NET Pull requests that update .NET code dependencies Pull requests that update a dependency file labels May 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment