Bump the dotnet-minor-patch group with 18 updates by dependabot[bot] · Pull Request #26 · TableMasterProject/TableMasterApi

dependabot · 2026-08-09T10:17:31Z

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 Dapper from 2.1.72 to 2.1.79.

Release notes

Sourced from Dapper's releases.

2.1.79 What's Changed

fix CI by @mgravell in fix CI DapperLib/Dapper#2196
Fix segfault when ICustomQueryParameter is a value type (#2189) by @andreasblueher in Fix segfault when ICustomQueryParameter is a value type (#2189) DapperLib/Dapper#2198
Update dependencies by @mgravell in Update dependencies DapperLib/Dapper#2202
Make private & internal classes sealed and less enumeration of lists & LINQ by @Henr1k80 in Make private & internal classes sealed and less enumeration of lists & LINQ DapperLib/Dapper#2197
Fix/prefer typehandlers for enums by @andreasblueher in Fix/prefer typehandlers for enums DapperLib/Dapper#2200
keep deps up to date by @mgravell in keep deps up to date DapperLib/Dapper#2204
Add ReferenceTrimmer and remove unused references by @dfederm in Add ReferenceTrimmer and remove unused references DapperLib/Dapper#2191

New Contributors

@andreasblueher made their first contribution in Fix segfault when ICustomQueryParameter is a value type (#2189) DapperLib/Dapper#2198
@Henr1k80 made their first contribution in Make private & internal classes sealed and less enumeration of lists & LINQ DapperLib/Dapper#2197
@dfederm made their first contribution in Add ReferenceTrimmer and remove unused references DapperLib/Dapper#2191

Full Changelog: DapperLib/Dapper@2.1.72...2.1.79

Commits viewable in compare view.

Updated FirebaseAdmin from 3.5.0 to 3.6.0.

Release notes

Sourced from FirebaseAdmin's releases.

3.6.0

New Features

feat(fcm): Enable fid and deprecate token for Send API (#525)

Bug Fixes

fix(ci): Resolve zizmor security findings in GitHub Actions workflows (#527)

Miscellaneous

[chore] Release 3.6.0 (#528)
chore(deps): bump NuGet/login from 1.1.0 to 1.2.0 (#520)
chore(deps): bump actions/checkout from 6.0.2 to 7.0.0 (#524)
chore: update System.Security.Cryptography.Xml to 8.0.3 (#518)

Commits viewable in compare view.

Updated FluentAssertions from 6.12.0 to 6.12.2.

Release notes

Sourced from FluentAssertions's releases.

6.12.2 What's Changed

Others

Better support for default interface and explicitly implemented properties by @dennisdoomen in Better support for default interface and explicitly implemented properties fluentassertions/fluentassertions#2794

Full Changelog: fluentassertions/fluentassertions@6.12.1...6.12.2

6.12.1 What's Changed

Improvements

Improve BeEmpty() and BeNullOrEmpty() performance for IEnumerable<T>, by materializing only the first item - #2530

Fixes

Fixed formatting error when checking nullable DateTimeOffset with BeWithin(...).Before(...) - #2312
BeEquivalentTo will now find and can map subject properties that are implemented through an explicitly-implemented interface - #2152
Fixed that the because and becauseArgs were not passed down the equivalency tree - #2318
BeEquivalentTo can again compare a non-generic IDictionary with a generic one - #2358
Fixed that the FormattingOptions were not respected in inner AssertionScope - #2329
Capitalize true and false in failure messages and make them formattable to a custom BooleanFormatter - #2390, #2393
Improved the failure message for NotBeOfType when wrapped in an AssertionScope and the subject is null - #2399
Improved the failure message for BeWritable/BeReadable when wrapped in an AssertionScope and the subject is read-only/write-only - #2399
Improved the failure message for ThrowExactly[Async] when wrapped in an AssertionScope and no exception is thrown - #2398
Improved the failure message for [Not]HaveExplicitProperty when wrapped in an AssertionScope and not implementing the interface - #2403
Improved the failure message for [Not]HaveExplicitMethod when wrapped in an AssertionScope and not implementing the interface - #2403
Changed BeEquivalentTo to exclude private protected members from the comparison - #2417
Fixed using BeEquivalentTo on an empty ArraySegment - #2445, #2511
BeEquivalentTo with a custom comparer can now handle null values - #2489
Ensured that nested calls to AssertionScope(context) create a chained context - #2607
One overload of the AssertionScope constructor would not create an actual scope associated with the thread - #2607
Fixed ThrowWithinAsync not respecting OperationCanceledException - #2614
Fixed using BeEquivalentTo with an IEqualityComparer targeting nullable types - #2648

Full Changelog: fluentassertions/fluentassertions@6.12.0...6.12.1

Commits viewable in compare view.

Updated Microsoft.AspNetCore.Authentication.JwtBearer from 10.0.7 to 10.0.10.

Release notes

Sourced from Microsoft.AspNetCore.Authentication.JwtBearer's releases.