chore(deps): update dependency mediatr to v12 #939
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.
This PR contains the following updates:
9.0.0
->12.4.1
Release Notes
jbogard/MediatR (MediatR)
v12.4.1
What's Changed
Full Changelog: jbogard/MediatR@v12.4.0...v12.4.1
v12.4.0
What's Changed
Full Changelog: jbogard/MediatR@v12.3.0...v12.4.0
v12.3.0
What's Changed
New Contributors
Full Changelog: jbogard/MediatR@v12.2.0...v12.3.0
v12.2.0
What's Changed
Full Changelog: jbogard/MediatR@v12.1.1...v12.2.0
v12.1.1
What's Changed
Full Changelog: jbogard/MediatR@v12.1.0...v12.1.1
v12.1.0
Migration Guide
https://github.com/jbogard/MediatR/wiki/Migration-Guide-12.0-to-12.1
What's Changed
New Contributors
Full Changelog: jbogard/MediatR@v12.0.1...v12.1.0
This release removes all scanning around behaviors, stream behaviors, and pre/post processors. That proved too problematic so you MUST register each of these explicitly with the appropriate registration methods inside
AddMediatR
. This also ensures that the order of behaviors and pre/post processors reflects the explicit order of registration. With the scanning approach, you couldn't control the order.v12.0.1
What's Changed
New Contributors
Full Changelog: jbogard/MediatR@v12.0.0...v12.0.1
v12.0.0
What's Changed
New Contributors
Migration Guide
Full Changelog: jbogard/MediatR@v11.1.0...v12.0.0
v11.1.0
What's Changed
New Contributors
Full Changelog: jbogard/MediatR@v11.0.0...v11.1.0
v11.0.0
What's Changed
New Contributors
Full Changelog: jbogard/MediatR@v10.0.1...v11.0.0
Migration Guide: https://github.com/jbogard/MediatR/wiki/Migration-Guide-10.x-to-11.0
v10.0.1
: 10.0.1This is a patch release to support the latest Contracts package, which changed its targets to
netstandard2.0
andnet461
.Although MediatR supports only
netstandard2.1
and above, it should not force the consumers of the contracts as such.v10.0.0
: 10.0.0This release adds support for
IAsyncEnumerable<T>
. A new request type,IStreamRequest<T>
represents a request to create a stream, with a new handler typeIStreamRequestHandler<TRequest, TResponse>
to handle. An example:Where the work inside of the handler would likely be calling some other streaming API, such as gRPC, EF Core streaming support, Dapper streaming etc.
There are also separate behaviors, with
IStreamPipelineBehavior
that are separate from the normalIPipelineBehavior
.With the addition of
IAsyncEnumerable
, this release now targetsnetstandard2.1
exclusively.There are some breaking API changes, called out in the 10.0 migration guide.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.