Skip to content

Bump Foundatio.Mediator.Abstractions from 1.2.1 to 1.3.1#343

Merged
github-actions[bot] merged 1 commit into
mainfrom
dependabot/nuget/Foundatio.Mediator.Abstractions-1.3.1
Jun 17, 2026
Merged

Bump Foundatio.Mediator.Abstractions from 1.2.1 to 1.3.1#343
github-actions[bot] merged 1 commit into
mainfrom
dependabot/nuget/Foundatio.Mediator.Abstractions-1.3.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 16, 2026

Copy link
Copy Markdown
Contributor

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).
  • Auto-detected Result.Invalid() status codes are now documented with .ProducesValidationProblem() (matching the HttpValidationProblemDetails body the mapper returns).
  • MediatorResultMapperOptions<TResult>.MapValue<TValue>(...) — value-shape result mapping (with an optional predicate), evaluated before status mappers.

Named endpoint groups (#​238)

  • New assembly-level [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.
  • Policies and ExcludeFromDescription added to the class-level [HandlerEndpointGroup] as well.

Custom request-body binding (#​238)

  • The generator now omits [FromBody] when the message type defines its own minimal-API binding (IBindableFromHttpContext<TSelf> or a static BindAsync), 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)

  • *Id message 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 singular SuccessStatusCode (int) property was replaced with the plural SuccessStatusCodes (int[]). Update any usages.

Features

  • Endpoint success metadata & result-mapping options (#​199) — Success result factories (Result.Created(), Result.Accepted(), Result.NoContent()) are detected and emit matching response metadata. Adds MediatorResultMapperOptions<TResult> plus DI/builder helpers to override specific ResultStatus → HTTP mappings without replacing the whole mapper (full IMediatorResultMapper<IResult> replacement is still supported). Result.Invalid() keeps ASP.NET Core's default ValidationProblem behavior.
  • Endpoint content-type metadata (#​200) — AcceptsContentTypes and ProducesContentTypes on [HandlerEndpoint] generate .Accepts<T>(...) / .Produces<T>(...) OpenAPI metadata.
  • Explicit route-template parameter binding (#​232) — A {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) returned 400.
  • Form / file upload endpoints (#​233) — Handlers whose message exposes IFormFile, IFormFileCollection, or IFormCollection now generate multipart/form-data endpoints. 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)].
  • Exclude handlers by namespace — new HandlerExcludeNamespacePatterns on [assembly: MediatorConfiguration] excludes handlers in matching namespaces from generation and discovery (exact match or trailing-wildcard prefix, e.g. "MyCompany.Messaging.*").

Dependencies

  • Numerous dependency updates, including WolverineFx (5.31.1 → 6.3.2), MassTransit (9.0.1 → 9.1.1), Immediate.Handlers, Scalar.AspNetCore, Scriban, Verify.XunitV3, and the Microsoft.Extensions.* / Microsoft.AspNetCore.* packages. See the full changelog.

Full Changelog: FoundatioFx/Foundatio.Mediator@v1.2.1...v1.3.0

Commits viewable in compare view.

@dependabot dependabot Bot added .NET Pull requests that update .NET code dependencies Pull requests that update a dependency file labels Jun 16, 2026
---
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>
@dependabot dependabot Bot force-pushed the dependabot/nuget/Foundatio.Mediator.Abstractions-1.3.1 branch from 352cc8e to f9d5327 Compare June 17, 2026 07:30
@github-actions github-actions Bot merged commit ee8d816 into main Jun 17, 2026
2 of 3 checks passed
@dependabot dependabot Bot deleted the dependabot/nuget/Foundatio.Mediator.Abstractions-1.3.1 branch June 17, 2026 07:31
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.

0 participants