chore: Bump the nuget-minor group with 12 updates by dependabot[bot] · Pull Request #513 · EcAuth/EcAuth

dependabot · 2026-08-07T12:33:47Z

Updated Asp.Versioning.Mvc from 10.0.0 to 10.2.1.

Release notes

Sourced from Asp.Versioning.Mvc's releases.

10.2.0

This release includes some big new features but is fully backward compatible with 10.0.0. The new features include versioned model member filtering, Roslyn analyzers, gRPC preview support, and a number of servicing patches since the previous release.

Fixes

All Platforms

Parsing an API version whose status ends in '.' no longer succeeds silently
Very large padding values in a format string no longer cause a stack overflow
Incorrect lower and upper bounds when matching API version ranges
Parsing a positive integer no longer allows whitespace or a leading '-'

ASP.NET Core

Routes are no longer incorrectly evicted from the route table (#1138)
Fixed routing of unversioned endpoints
Fixed extracting an API version that includes a status when versioning by URL segment (#1187)
A user-registered IProblemDetailsWriter is preserved by AddApiVersioning() (#1191)

ASP.NET Core OpenAPI

Support for more XML comment tags (#1205)
Fixed the error message reported for an unmapped JSON property
Fixed descriptions applied to filtered members

Features

All Platforms

New ApiVersionRange type for matching a set of API versions using the same interval notation as a package version
- 1.0 → x ≥ 1.0
- [1.0] → x == 1.0
- (1.0,) → x > 1.0
- (,1.0] → x ≤ 1.0
- [1.0,2.0) → 1.0 ≤ x < 2.0
- Multiple rules are combined as a logical or; ApiVersionRange.Any and ApiVersionRange.Empty are provided for
  the degenerate cases
- A range matches API versions; it does not define them. API versions must still be explicitly declared
New VisibleInApiVersionAttribute indicates the range of API versions a data member is visible in; for example,
[VisibleInApiVersion("2.0")]
New IAnnotation<TKey, TValue> abstraction for associating out-of-band metadata with a member
[StringSyntax] is now applied to API version inputs so the IDE and analyzers understand them; the recognized
syntaxes are ApiVersion, ApiVersionRange, and ApiVersionFormat

Analyzers

API Versioning now ships Roslyn analyzers. There is no new package to install — the core rules are packed into Asp.Versioning.Abstractions and the API rules are packed into Asp.Versioning.Http, so any application that already references API Versioning picks them up transitively.

There is an initial set of 31 rules. You can find all of the rule information in the new diagnostics wiki topic.

Notes:
... (truncated)

Commits viewable in compare view.

Updated Asp.Versioning.Mvc.ApiExplorer from 10.0.0 to 10.2.1.

Release notes

Sourced from Asp.Versioning.Mvc.ApiExplorer's releases.

10.2.0

This release includes some big new features but is fully backward compatible with 10.0.0. The new features include versioned model member filtering, Roslyn analyzers, gRPC preview support, and a number of servicing patches since the previous release.

Fixes

All Platforms

Parsing an API version whose status ends in '.' no longer succeeds silently
Very large padding values in a format string no longer cause a stack overflow
Incorrect lower and upper bounds when matching API version ranges
Parsing a positive integer no longer allows whitespace or a leading '-'

ASP.NET Core

Routes are no longer incorrectly evicted from the route table (#1138)
Fixed routing of unversioned endpoints
Fixed extracting an API version that includes a status when versioning by URL segment (#1187)
A user-registered IProblemDetailsWriter is preserved by AddApiVersioning() (#1191)

ASP.NET Core OpenAPI

Support for more XML comment tags (#1205)
Fixed the error message reported for an unmapped JSON property
Fixed descriptions applied to filtered members

Features

All Platforms

New ApiVersionRange type for matching a set of API versions using the same interval notation as a package version
- 1.0 → x ≥ 1.0
- [1.0] → x == 1.0
- (1.0,) → x > 1.0
- (,1.0] → x ≤ 1.0
- [1.0,2.0) → 1.0 ≤ x < 2.0
- Multiple rules are combined as a logical or; ApiVersionRange.Any and ApiVersionRange.Empty are provided for
  the degenerate cases
- A range matches API versions; it does not define them. API versions must still be explicitly declared
New VisibleInApiVersionAttribute indicates the range of API versions a data member is visible in; for example,
[VisibleInApiVersion("2.0")]
New IAnnotation<TKey, TValue> abstraction for associating out-of-band metadata with a member
[StringSyntax] is now applied to API version inputs so the IDE and analyzers understand them; the recognized
syntaxes are ApiVersion, ApiVersionRange, and ApiVersionFormat

Analyzers

API Versioning now ships Roslyn analyzers. There is no new package to install — the core rules are packed into Asp.Versioning.Abstractions and the API rules are packed into Asp.Versioning.Http, so any application that already references API Versioning picks them up transitively.

There is an initial set of 31 rules. You can find all of the rule information in the new diagnostics wiki topic.

Notes:
... (truncated)

Commits viewable in compare view.

Updated Azure.Monitor.OpenTelemetry.AspNetCore from 1.5.0 to 1.6.0.

Release notes

Sourced from Azure.Monitor.OpenTelemetry.AspNetCore's releases.

1.6.0 1.6.0 (2026-07-27)

Bugs Fixed

Hardened Azure Monitor ingestion and Live Metrics redirect handling to prevent credentials and telemetry from being forwarded to untrusted destinations.
(#61244)

Other Changes

Updated Azure.Monitor.OpenTelemetry.Exporter dependency to 1.8.3, which brings: customer SDK stats enabled by default (opt out with APPLICATIONINSIGHTS_SDKSTATS_DISABLED=true), internal Network SDK statistics signals, GenAI agent attribution processors for spans and logs, and CategoryName added to custom event custom dimensions.

Commits viewable in compare view.

Updated dotnet-ef from 10.0.6 to 10.0.10.

Release notes

Sourced from dotnet-ef's releases.