Bump Akka.Hosting.TestKit from 1.5.58 to 1.5.65

[dependabot]

Updated Akka.Hosting.TestKit from 1.5.58 to 1.5.65.

Release notes

Sourced from Akka.Hosting.TestKit's releases.

1.5.65

1.5.65 April 10th 2026

Updates

• Bump Akka version from 1.5.64 to 1.5.65

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

• Bump Akka version from 1.5.63 to 1.5.64

1.5.63

1.5.63 March 24th 2026

Bug Fixes

• Fix ActorRegistry.TryGet caching stale IActorRef values - ActorRegistry.TryGet was caching the internal IActorRef on first call.

Updates

• Bump Akka version from 1.5.62 to 1.5.63

1.5.62

1.5.62 March 4th 2026

Updates

• Bump Akka version from 1.5.61 to 1.5.62

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

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)

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

• 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

• 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

• Bump Akka version from 1.5.55 to 1.5.57

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

• 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

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

• 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

• Bump Akka version from 1.5.55 to 1.5.57

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

• Support custom health check registrations on Journal and Snapshot Builders - added API to support custom health check registrations for Akka.Persistence plugins, related to issue #​678
• Add support for custom certificate validation callbacks - integrated the new CertificateValidationCallback feature from Akka.NET v1.5.55, allowing users to provide custom certificate validation logic for SSL/TLS connections. Enables advanced scenarios including certificate pinning, subject/issuer matching, custom business validation rules, and advanced mTLS scenarios

Enhancements

• Add customizable tags parameter to health check methods - resolved issue #​679 by adding new overload allowing custom tags for health checks while maintaining backward compatibility
• Made it easier to customize failureState and tags for all health checks - simplified health check configuration API for all health checks

Updates

• Bump Akka version from 1.5.53 to 1.5.55

1.5.55-beta1 October 26th 2025

New Features

• Support custom health check registrations on Journal and Snapshot Builders - added API to support custom health check registrations for Akka.Persistence plugins, related to issue #​678

Enhancements

• Add customizable tags parameter to health check methods - resolved issue #​679 by adding new overload allowing custom tags for health checks while maintaining backward compatibility
• Made it easier to customize failureState and tags for all health checks - simplified health check configuration API for all health checks

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

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}