Bump Akka.Hosting from 1.5.60 to 1.5.61

[dependabot]

Updated Akka.Hosting from 1.5.60 to 1.5.61.

Release notes

Sourced from Akka.Hosting's releases.

1.5.61

1.5.61 February 26th 2026

Updates

• Bump Akka version from 1.5.60 to 1.5.61

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

• Fix WithDefaultLogMessageFormatter<T>() rejecting built-in formatters - SemanticLogMessageFormatter and DefaultLogMessageFormatter have private constructors (they use singleton Instance properties), but the validation only accepted public parameterless constructors. These built-in types are now correctly accepted.

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

• Bump Akka version from 1.5.59 to 1.5.60

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

• Fix semantic logging not capturing named placeholders as structured properties - resolved issue #​701 where named placeholders like {Event} in log messages were not captured as searchable structured properties. Made all LoggerConfigBuilder properties optional and refactored message formatting code.
• Fix TestKit startup timeout race condition - resolved race condition in TestKit.InitializeAsync() where CancellationTokenSource.Register() threw exceptions on the timer thread, causing unhandled exceptions that crashed the test host process. Also increased default startup timeout from 10s to 30s for CI environments.

Updates

• Bump Akka version from 1.5.58 to 1.5.59
• Added OpenTelemetry package dependency (1.9.0+) for trace correlation support

1.5.58 January 9th 2026

Updates

• Bump Akka version from 1.5.57 to 1.5.58

1.5.57 December 16th 2025

New Features
... (truncated)

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

[github-actions]

Test Results

  2 files  ±0    2 suites  ±0   1m 29s ⏱️ -2s
519 tests ±0  519 ✅ ±0  0 💤 ±0  0 ❌ ±0 
520 runs  ±0  520 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 3959344. ± Comparison against base commit d064a76.

♻️ This comment has been updated with latest results.

[Aaronontheweb]

@dependabot rebase