Bump Foundatio.Mediator.Abstractions from 1.2.1 to 1.3.1#343
Merged
github-actions[bot] merged 1 commit intoJun 17, 2026
Merged
Conversation
--- updated-dependencies: - dependency-name: Foundatio.Mediator.Abstractions dependency-version: 1.3.1 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
352cc8e to
f9d5327
Compare
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.
Pinned Foundatio.Mediator.Abstractions at 1.3.1.
Release notes
Sourced from Foundatio.Mediator.Abstractions's releases.
1.3.1
Endpoint generation improvements. All changes are additive and backward-compatible with 1.3.0.
Endpoint metadata options (#234)
[HandlerEndpoint(ExcludeFromDescription = true)]— hide an endpoint from OpenAPI/API explorers while keeping it routable.[HandlerEndpoint(DisplayName = "...")]— pin the ASP.NET Core endpoint display name (logs/diagnostics).Result.Invalid()status codes are now documented with.ProducesValidationProblem()(matching theHttpValidationProblemDetailsbody the mapper returns).MediatorResultMapperOptions<TResult>.MapValue<TValue>(...)— value-shape result mapping (with an optional predicate), evaluated before status mappers.Named endpoint groups (#238)
[MediatorEndpointGroup(Name, RoutePrefix, Tags, EndpointFilters, Policies, ExcludeFromDescription)], referenced by[HandlerEndpoint(Group = "...")], so handlers across classes share one route prefix, tags, filters, and authorization policies under a single group.PoliciesandExcludeFromDescriptionadded to the class-level[HandlerEndpointGroup]as well.Custom request-body binding (#238)
[FromBody]when the message type defines its own minimal-API binding (IBindableFromHttpContext<TSelf>or a staticBindAsync), so ASP.NET Core's custom binding is no longer preempted — enabling non-standard bodies (JSON Patch, legacy partial JSON, XML) through platform seams.Binding fix (#236)
*Idmessage properties are no longer bound as route/query parameters for body commands with an explicit route that lacks the matching placeholder. Use[FromBody]on the message parameter to force whole-message body binding.Full changelog: FoundatioFx/Foundatio.Mediator@v1.3.0...v1.3.1
1.3.0
Breaking Changes
[HandlerEndpoint(SuccessStatusCode = …)]→SuccessStatusCodes(#199) — the singularSuccessStatusCode(int) property was replaced with the pluralSuccessStatusCodes(int[]). Update any usages.Features
Result.Created(),Result.Accepted(),Result.NoContent()) are detected and emit matching response metadata. AddsMediatorResultMapperOptions<TResult>plus DI/builder helpers to override specificResultStatus → HTTPmappings without replacing the whole mapper (fullIMediatorResultMapper<IResult>replacement is still supported).Result.Invalid()keeps ASP.NET Core's defaultValidationProblembehavior.AcceptsContentTypesandProducesContentTypeson[HandlerEndpoint]generate.Accepts<T>(...)/.Produces<T>(...)OpenAPI metadata.{placeholder}in an explicit[HandlerEndpoint(..., "Path/{param}")]template now binds from the route regardless of property naming or HTTP method. Previously the value was emitted as[FromQuery], so path-only requests (e.g.GET /contracts/H-42) returned400.IFormFile,IFormFileCollection, orIFormCollectionnow generatemultipart/form-dataendpoints. File properties bind by name, other fields bind via[FromForm], route placeholders still bind from the route. Antiforgery (CSRF) validation stays required by default — disable it explicitly per endpoint with[HandlerEndpoint(DisableAntiforgery = true)]or assembly-wide with[assembly: MediatorConfiguration(EndpointDisableAntiforgery = true)].HandlerExcludeNamespacePatternson[assembly: MediatorConfiguration]excludes handlers in matching namespaces from generation and discovery (exact match or trailing-wildcard prefix, e.g."MyCompany.Messaging.*").Dependencies
Full Changelog: FoundatioFx/Foundatio.Mediator@v1.2.1...v1.3.0
Commits viewable in compare view.