Skip to content

Bump WolverineFx from 5.2.0 to 5.7.1#624

Closed
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/nuget/src/DataFacade/WolverineFx-5.7.1
Closed

Bump WolverineFx from 5.2.0 to 5.7.1#624
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/nuget/src/DataFacade/WolverineFx-5.7.1

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 15, 2025

Updated WolverineFx from 5.2.0 to 5.7.1.

Release notes

Sourced from WolverineFx's releases.

5.7.1

What's Changed

Full Changelog: JasperFx/wolverine@V5.7.0...V5.7.1

5.7.0

Also see: https://github.com/JasperFx/wolverine/milestone/54?closed=1 for more information about the issues closed

What's Changed

New Contributors

Full Changelog: JasperFx/wolverine@V5.6.0...V5.7.0

5.6.0

What's Changed

Full Changelog: JasperFx/wolverine@V5.5.0...V5.6.0

5.5.0

What's Changed

Full Changelog: JasperFx/wolverine@V5.4.3...V5.5.0

5.4.3

What's Changed

Full Changelog: JasperFx/wolverine@V5.4.2...V5.4.3

5.4.2

What's Changed

Full Changelog: JasperFx/wolverine@V5.4.1...V5.4.2

5.4.1

This is a pretty significant bug fix release for some of the new idempotency checks, inbox cleanup, and CloudEvents + durable endpoints.

What's Changed

New Contributors

Full Changelog: JasperFx/wolverine@V5.4.0...V5.4.1

5.4.0

What's Changed

Full Changelog: JasperFx/wolverine@V5.3.0...V5.4.0

5.3.0

What's Changed

Full Changelog: JasperFx/wolverine@V5.2.0...V5.3.0

Commits viewable in compare view.

Dependabot compatibility score

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 merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @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)

---
updated-dependencies:
- dependency-name: WolverineFx
  dependency-version: 5.7.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added .NET Pull requests that update .net code dependencies Pull requests that update a dependency file labels Dec 15, 2025
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Dec 27, 2025

Looks like WolverineFx is no longer updatable, so this is no longer needed.

@dependabot dependabot bot closed this Dec 27, 2025
@dependabot dependabot bot deleted the dependabot/nuget/src/DataFacade/WolverineFx-5.7.1 branch December 27, 2025 01:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file .NET Pull requests that update .net code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bug: Multi-tenant Postgres Transport Always Uses Wrong Sender Due to database.Name Being Always "Default"

0 participants