Bump Akka.Cluster.Hosting from 1.5.42 to 1.5.65#342
Open
dependabot[bot] wants to merge 1 commit intodevfrom
Open
Bump Akka.Cluster.Hosting from 1.5.42 to 1.5.65#342dependabot[bot] wants to merge 1 commit intodevfrom
dependabot[bot] wants to merge 1 commit intodevfrom
Conversation
--- updated-dependencies: - dependency-name: Akka.Cluster.Hosting dependency-version: 1.5.65 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.42 to 1.5.65.
Release notes
Sourced from Akka.Cluster.Hosting's releases.
1.5.65
1.5.65 April 10th 2026
Updates
1.5.64
1.5.64 March 31st 2026
Bug Fixes
LoggerFactoryLoggermetadata regression for non-semantic logs - PR #706 (trace correlation) accidentally gatedActorPath,LogSource,Timestamp, andThreademission on_hasSemanticProperties, which wasfalsefor plain-string logs. Non-semantic logs lost all structured metadata, breaking downstream consumers such as Datadog pipelines and customConsoleFormatters. All log paths now emit the full set of Akka metadata as structured attributes regardless of whether the message uses named placeholders.Breaking Changes
Akka.Hosting.TestKitto xUnit 3 -Akka.Hosting.TestKitnow targets xUnit v3. Users who need to remain on xUnit v2 can switch to the newAkka.Hosting.TestKit.Xunit2package, which preserves the previous xUnit v2-based TestKit API.Updates
1.5.63
1.5.63 March 24th 2026
Bug Fixes
ActorRegistry.TryGetcaching staleIActorRefvalues -ActorRegistry.TryGetwas caching the internalIActorRefon first call.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
Activity.Currentdoesn't flow across actor mailbox boundaries because it usesAsyncLocal<T>. When using Akka.NET 1.5.59+,LogEvent.ActivityContextcaptures trace context at log creation time and flows it through to OpenTelemetryLogRecords via the newAkkaTraceContextProcessor. Register withoptions.AddAkkaTraceCorrelation()in your OpenTelemetry logging configuration.WithContext()logging context enrichment works automatically withLoggerFactoryLogger. Context properties set via the coreWithContext()API flow through to Microsoft.Extensions.Logging state dictionaries viaTryGetProperties()without any code changes needed.Bug Fixes
WithDefaultLogMessageFormatter<T>()rejecting built-in formatters -SemanticLogMessageFormatterandDefaultLogMessageFormatterhave private constructors (they use singletonInstanceproperties), but the validation only accepted public parameterless constructors. These built-in types are now correctly accepted.Deprecations
WithDefaultLogMessageFormatter<T>()is now marked[Obsolete]—SemanticLogMessageFormatteris the default as of Akka.NET 1.5.58 and no longer needs to be set explicitly. The method still works for customILogMessageFormatterimplementations.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
Activity.Currentdoesn't flow across actor mailbox boundaries because it usesAsyncLocal<T>. When using Akka.NET 1.5.59+,LogEvent.ActivityContextcaptures trace context at log creation time and flows it through to OpenTelemetryLogRecords via the newAkkaTraceContextProcessor. Register withoptions.AddAkkaTraceCorrelation()in your OpenTelemetry logging configuration.1.5.59 January 2026
New Features
Activity.Currentdoesn't flow across actor mailbox boundaries because it usesAsyncLocal<T>. When using Akka.NET 1.5.59+,LogEvent.ActivityContextcaptures trace context at log creation time and flows it through to OpenTelemetryLogRecords via the newAkkaTraceContextProcessor. Register withoptions.AddAkkaTraceCorrelation()in your OpenTelemetry logging configuration.Bug Fixes
{Event}in log messages were not captured as searchable structured properties. Made allLoggerConfigBuilderproperties optional and refactored message formatting code.TestKit.InitializeAsync()whereCancellationTokenSource.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
OpenTelemetrypackage dependency (1.9.0+) for trace correlation support1.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
Activity.Currentdoesn't flow across actor mailbox boundaries because it usesAsyncLocal<T>. When using Akka.NET 1.5.59+,LogEvent.ActivityContextcaptures trace context at log creation time and flows it through to OpenTelemetryLogRecords via the newAkkaTraceContextProcessor. Register withoptions.AddAkkaTraceCorrelation()in your OpenTelemetry logging configuration.WithContext()logging context enrichment works automatically withLoggerFactoryLogger. Context properties set via the coreWithContext()API flow through to Microsoft.Extensions.Logging state dictionaries viaTryGetProperties()without any code changes needed.Bug Fixes
WithDefaultLogMessageFormatter<T>()rejecting built-in formatters -SemanticLogMessageFormatterandDefaultLogMessageFormatterhave private constructors (they use singletonInstanceproperties), but the validation only accepted public parameterless constructors. These built-in types are now correctly accepted.Deprecations
WithDefaultLogMessageFormatter<T>()is now marked[Obsolete]—SemanticLogMessageFormatteris the default as of Akka.NET 1.5.58 and no longer needs to be set explicitly. The method still works for customILogMessageFormatterimplementations.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
Activity.Currentdoesn't flow across actor mailbox boundaries because it usesAsyncLocal<T>. When using Akka.NET 1.5.59+,LogEvent.ActivityContextcaptures trace context at log creation time and flows it through to OpenTelemetryLogRecords via the newAkkaTraceContextProcessor. Register withoptions.AddAkkaTraceCorrelation()in your OpenTelemetry logging configuration.1.5.59 January 2026
New Features
Activity.Currentdoesn't flow across actor mailbox boundaries because it usesAsyncLocal<T>. When using Akka.NET 1.5.59+,LogEvent.ActivityContextcaptures trace context at log creation time and flows it through to OpenTelemetryLogRecords via the newAkkaTraceContextProcessor. Register withoptions.AddAkkaTraceCorrelation()in your OpenTelemetry logging configuration.Bug Fixes
{Event}in log messages were not captured as searchable structured properties. Made allLoggerConfigBuilderproperties optional and refactored message formatting code.TestKit.InitializeAsync()whereCancellationTokenSource.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
OpenTelemetrypackage dependency (1.9.0+) for trace correlation support1.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
Activity.Currentdoesn't flow across actor mailbox boundaries because it usesAsyncLocal<T>. When using Akka.NET 1.5.59+,LogEvent.ActivityContextcaptures trace context at log creation time and flows it through to OpenTelemetryLogRecords via the newAkkaTraceContextProcessor. Register withoptions.AddAkkaTraceCorrelation()in your OpenTelemetry logging configuration.WithContext()logging context enrichment works automatically withLoggerFactoryLogger. Context properties set via the coreWithContext()API flow through to Microsoft.Extensions.Logging state dictionaries viaTryGetProperties()without any code changes needed.Bug Fixes
WithDefaultLogMessageFormatter<T>()rejecting built-in formatters -SemanticLogMessageFormatterandDefaultLogMessageFormatterhave private constructors (they use singletonInstanceproperties), but the validation only accepted public parameterless constructors. These built-in types are now correctly accepted.Deprecations
WithDefaultLogMessageFormatter<T>()is now marked[Obsolete]—SemanticLogMessageFormatteris the default as of Akka.NET 1.5.58 and no longer needs to be set explicitly. The method still works for customILogMessageFormatterimplementations.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
Activity.Currentdoesn't flow across actor mailbox boundaries because it usesAsyncLocal<T>. When using Akka.NET 1.5.59+,LogEvent.ActivityContextcaptures trace context at log creation time and flows it through to OpenTelemetryLogRecords via the newAkkaTraceContextProcessor. Register withoptions.AddAkkaTraceCorrelation()in your OpenTelemetry logging configuration.1.5.59 January 2026
New Features
Activity.Currentdoesn't flow across actor mailbox boundaries because it usesAsyncLocal<T>. When using Akka.NET 1.5.59+,LogEvent.ActivityContextcaptures trace context at log creation time and flows it through to OpenTelemetryLogRecords via the newAkkaTraceContextProcessor. Register withoptions.AddAkkaTraceCorrelation()in your OpenTelemetry logging configuration.Bug Fixes
{Event}in log messages were not captured as searchable structured properties. Made allLoggerConfigBuilderproperties optional and refactored message formatting code.TestKit.InitializeAsync()whereCancellationTokenSource.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
OpenTelemetrypackage dependency (1.9.0+) for trace correlation support1.5.58 January 9th 2026
Updates
1.5.57 December 16th 2025
New Features
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
Activity.Currentdoesn't flow across actor mailbox boundaries because it usesAsyncLocal<T>. When using Akka.NET 1.5.59+,LogEvent.ActivityContextcaptures trace context at log creation time and flows it through to OpenTelemetryLogRecords via the newAkkaTraceContextProcessor. Register withoptions.AddAkkaTraceCorrelation()in your OpenTelemetry logging configuration.1.5.59
1.5.59 January 26th 2026
Bug Fixes
{Event}in log messages were not captured as searchable structured properties. Made allLoggerConfigBuilderproperties optional and refactored message formatting code.TestKit.InitializeAsync()whereCancellationTokenSource.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
1.5.58 January 9th 2026
Updates
1.5.57 December 16th 2025
New Features
Updates
1.5.55.1 October 27th 2025
Enhancements
Optionsproperty toAkkaPersistenceJournalBuilderandAkkaPersistenceSnapshotBuilder. 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 features1.5.55 October 26th 2025
New Features
CertificateValidationCallbackfeature 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 scenariosEnhancements
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
Updates
1.5.55.1 October 27th 2025
Enhancements
Optionsproperty toAkkaPersistenceJournalBuilderandAkkaPersistenceSnapshotBuilder. 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 features1.5.55 October 26th 2025
New Features
CertificateValidationCallbackfeature 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 scenariosEnhancements
Updates
1.5.55-beta1 October 26th 2025
New Features
Enhancements
Updates
1.5.53 October 14th 2025
Bug Fixes
JournalOptions.Adaptersproperty. The issue was caused by unnecessary fallback configuration that interfered with adapter registration during HOCON merging.Updates
... (truncated)
1.5.57
1.5.57 December 16th 2025
New Features
Updates
1.5.55.1 October 27th 2025
Enhancements
Optionsproperty toAkkaPersistenceJournalBuilderandAkkaPersistenceSnapshotBuilder. 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 features1.5.55 October 26th 2025
New Features
CertificateValidationCallbackfeature 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 scenariosEnhancements
Updates
1.5.55-beta1 October 26th 2025
New Features
Enhancements
Updates
1.5.53 October 14th 2025
Bug Fixes
JournalOptions.Adaptersproperty. 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
Updates
1.5.55.1 October 27th 2025
Enhancements
Optionsproperty toAkkaPersistenceJournalBuilderandAkkaPersistenceSnapshotBuilder. 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 features1.5.55 October 26th 2025
New Features
CertificateValidationCallbackfeature 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 scenariosEnhancements
Updates
1.5.55-beta1 October 26th 2025
New Features
Enhancements
Updates
1.5.53 October 14th 2025
Bug Fixes
JournalOptions.Adaptersproperty. 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
Optionsproperty toAkkaPersistenceJournalBuilderandAkkaPersistenceSnapshotBuilder. 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 features1.5.55 October 26th 2025
New Features
CertificateValidationCallbackfeature 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 scenariosEnhancements
Updates
1.5.55-beta1 October 26th 2025
New Features
Enhancements
Updates
1.5.53 October 14th 2025
Bug Fixes
JournalOptions.Adaptersproperty. 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
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 October 2nd 2025
Bug Fixes
... (truncated)
1.5.55
1.5.55 October 26th 2025
New Features
CertificateValidationCallbackfeature 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 scenariosEnhancements
Updates
1.5.55-beta1 October 26th 2025
New Features
Enhancements
Updates
1.5.53 October 14th 2025
Bug Fixes
JournalOptions.Adaptersproperty. 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
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 October 2nd 2025
Bug Fixes
.WithHealthCheck()without adding event adapters1.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
JournalOptions.Adaptersproperty. 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
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 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.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) ## 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) Commits viewable in [compare view](https://github.com/akkadotnet/Akka.Hosting/compare/1.5.42...1.5.65). </details> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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 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>