Bump Akka.Persistence.MongoDb from 1.5.42 to 1.5.53 #10
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.Persistence.MongoDb from 1.5.42 to 1.5.53.
Release notes
Sourced from Akka.Persistence.MongoDb's releases.
1.5.53
1.5.53 October 16th 2025
New Feature: Health Check Support for Akka.Persistence.MongoDb.Hosting
This release adds built-in health check support for MongoDB journal and snapshot stores, integrated with Microsoft.Extensions.Diagnostics.HealthChecks. This enables monitoring and observability for your MongoDB persistence plugins.
Key capabilities:
akka,persistence,mongodb)Example usage:
For complete documentation, see the Akka.Persistence.MongoDb.Hosting README and the main README.
1.5.42 May 22nd 2025
We're optimizing how write transaction is being done. Following the MongoDb documentation that all single document writes are atomic, we're not using transaction for single document writes anymore.
1.5.41-beta1 April 4th 2025
We're optimizing how write transaction is being done. Following the MongoDb documentation that all single document writes are atomic, we're not using transaction for single document writes anymore.
1.5.40 March 27th 2025
... (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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)