Skip to content

Akka.Hosting 1.5.62

Choose a tag to compare

@github-actionsgithub-actions released this 03 Mar 20:34
a747742

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

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

Updates

1.5.51.1 October 2nd 2025

Bug Fixes

1.5.51 October 1st 2025

New Features

Updates