Skip to content

deps: Bump the dotnet-dependencies group with 19 updates#5

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/ShopInventory.Web/dotnet-dependencies-62ef222c03
Open

deps: Bump the dotnet-dependencies group with 19 updates#5
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/ShopInventory.Web/dotnet-dependencies-62ef222c03

Conversation

@dependabot
Copy link
Copy Markdown

@dependabot dependabot Bot commented on behalf of github May 18, 2026

Updated Asp.Versioning.Mvc from 8.1.0 to 10.0.0.

Release notes

Sourced from Asp.Versioning.Mvc's releases.

10.0.0

The official release for 10.0 is here! In addition to the changes in the preview releases, there are a few additional changes.

Features

All Platforms

  • ApiVersionAttribute, MapToVersionAttribute, and AdvertiseApiVersionsAttribute all now have a constructor which can support the date format without being a string; for example, [ApiVersion(2026, 04, 01)]

ASP.NET Core OpenAPI

  • XmlCommentsTransformer is now resolved via DI, which allows it to be re-registered with a user-defined file path
  • Public types and members are now virtual for developer extensibility

Fixes

ASP.NET Core OpenAPI

  • Fix comparison between entry and calling assembly (#​1175)
  • Ensure keyed services are registered with a lowercase key (#​1176)
  • Fix nested key service resolution (#​1177)
  • Implement IKeyedServiceProvider when injecting ApiVersion (#​1178)

Breaking Changes

ASP.NET Core OpenAPI

  • OpenAPI documents use "enum": ["1.0"] instead of "default": "1.0"
    • This has a similar effect, but removes the free-form input when the value is bounded
    • When optional, the enum value can still be deleted/removed
    • Some UIs, such as Scalar, still provide a way to provide an enumerated value that isn't in the list

Release Notes

  • Asp.Versioning.OData is being released as rc.1 because Microsoft.AspNetCore.OData is only at preview.2
  • Asp.Versioning.OpenAPI is being released as rc.1 pending the outcome of dotnet/aspnetcore#​66408
    • If the package can be released without requiring the explicit use of Reflection, that is the preference
    • No additional changes are planned unless bugs are reported

Feedback

Thanks to the contributors on this release whether it was code contributions or test driving the previews. Special thanks to @​sander1095 for being a strong advocate and helping to bring even more visibility to the project.

10.0.0-preview.2

This release is a quick iteration which contains minor fixes based on feedback from Preview 1.

Trying out previews is always a big ask. The OpenAPI extensions are net new, so I really am looking for some community support to flush out any edge cases I may have been missed before releasing officially. All other libraries are stable.

Aside from whatever the community may report, there are only two final things I'm considering for the final release:

  1. gRPC versioning support, which I'm waiting on grpc/grpc-dotnet#​2690 and grpc/grpc-dotnet#​2693
  2. Coordination with Microsoft to open up types in Microsoft.AspNetCore.OpenAPI so I don't have to resort to Reflection for integration

If these are not able to be completed within the next few weeks, then I will officially release the stable libraries. The gRPC support will then come in a future, likely minor version, release. The OpenAPI extensions may stay in preview as AOT will likely be broken.

Features

All Platforms

  • Support _ prefix character when extracting API versions from a .NET namespace (#​1172)
  • Generate software bill of materials (SBOM) (#​1100)

Fixes

ASP.NET Core with OpenAPI

  • Build-time OpenAPI documents have empty paths (#​1165, #​1168)
  • Missing XML Comments (#​1169)
  • Support <example> tags (#​1170)

Breaking Changes

The OpenAPI extensions for API Versioning (e.g. x-api-versioning) will now use a nested links property rather than a simple array. This allows the schema to be open for possible future enhancements.

Preview 1

{
    "x-api-versioning":
    [
        {
            "title": "Version Policy",
            "type": "text/html",
            "rel": "info",
            "url": "http://my.api.com/policies/versioning.html"
        }
    ]
}

Preview 2+

{
 ... (truncated)

## 10.0.0-preview.1

This is a major release that includes new, publicly visible API changes as well as a rollup of bug fixes. This is an initial preview release that is primarily focused on improving OpenAPI integration. Additional features will come in the next preview. The wiki has not be fully updated - yet, but that will also occur in the near future.

These are preview features and changes. Please report issues if you find them. Feel free to start a [discussion](../../discussions) about the changes in the forthcoming official release.

# Features

## All Platforms

- Support for the `deprecation` response header as defined by [RFC 9745](https://www.rfc-editor.org/rfc/rfc9745.html) (#​1128)

## ASP.NET Core

- Integration with the [Microsoft.AspNetCore.OpenApi](https://www.nuget.org/packages/Microsoft.AspNetCore.OpenApi) library
  - These features in the new [Asp.Versioning.OpenApi](https://www.nuget.org/packages/Asp.Versioning.OpenApi) library
  - OpenAPI documents are now generated per API version
  - Sunset and deprecation policies are automatically included with standard (English) text, but can be customized
  - Sunset and deprecation policies links are included in OpenAPI documents via the `x-api-versioning` extension
  - The versioned `HttpClient` can now read and report on sunset and deprecation policies
  - All [example projects](../../tree/main/examples/AspNetCore) have been updated to use [Scalar](https://scalar.com/)

### Example

The following provides an example of a bare minimum setup:

```c#
var builder = WebApplication.CreateBuilder( args );
var services = builder.Services;

services.AddApiVersioning()
        .AddApiExplorer()
        .AddOpenApi();

var app = builder.Build();
var hello = app.NewVersionedApi( "HelloWorld" );
var v1 = hello.MapGroup( "/hello-world" ).HasApiVersion( 1.0 );
var v2 = hello.MapGroup( "/hello-world" ).HasApiVersion( 2.0 );

v1.MapGet( "/", ( ApiVersion version ) => $"Hello world from v{version}" );
v2.MapGet( "/", ( ApiVersion version ) => $"Hello world from v{version}" );

if ( app.Environment.IsDevelopment() )
{
    app.MapOpenApi().WithDocumentPerVersion();
}

app.Run();

The key differences from what you may be currently doing:

... (truncated)

Commits viewable in compare view.

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

Release notes

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

10.0.0

The official release for 10.0 is here! In addition to the changes in the preview releases, there are a few additional changes.

Features

All Platforms

  • ApiVersionAttribute, MapToVersionAttribute, and AdvertiseApiVersionsAttribute all now have a constructor which can support the date format without being a string; for example, [ApiVersion(2026, 04, 01)]

ASP.NET Core OpenAPI

  • XmlCommentsTransformer is now resolved via DI, which allows it to be re-registered with a user-defined file path
  • Public types and members are now virtual for developer extensibility

Fixes

ASP.NET Core OpenAPI

  • Fix comparison between entry and calling assembly (#​1175)
  • Ensure keyed services are registered with a lowercase key (#​1176)
  • Fix nested key service resolution (#​1177)
  • Implement IKeyedServiceProvider when injecting ApiVersion (#​1178)

Breaking Changes

ASP.NET Core OpenAPI

  • OpenAPI documents use "enum": ["1.0"] instead of "default": "1.0"
    • This has a similar effect, but removes the free-form input when the value is bounded
    • When optional, the enum value can still be deleted/removed
    • Some UIs, such as Scalar, still provide a way to provide an enumerated value that isn't in the list

Release Notes

  • Asp.Versioning.OData is being released as rc.1 because Microsoft.AspNetCore.OData is only at preview.2
  • Asp.Versioning.OpenAPI is being released as rc.1 pending the outcome of dotnet/aspnetcore#​66408
    • If the package can be released without requiring the explicit use of Reflection, that is the preference
    • No additional changes are planned unless bugs are reported

Feedback

Thanks to the contributors on this release whether it was code contributions or test driving the previews. Special thanks to @​sander1095 for being a strong advocate and helping to bring even more visibility to the project.

10.0.0-preview.2

This release is a quick iteration which contains minor fixes based on feedback from Preview 1.

Trying out previews is always a big ask. The OpenAPI extensions are net new, so I really am looking for some community support to flush out any edge cases I may have been missed before releasing officially. All other libraries are stable.

Aside from whatever the community may report, there are only two final things I'm considering for the final release:

  1. gRPC versioning support, which I'm waiting on grpc/grpc-dotnet#​2690 and grpc/grpc-dotnet#​2693
  2. Coordination with Microsoft to open up types in Microsoft.AspNetCore.OpenAPI so I don't have to resort to Reflection for integration

If these are not able to be completed within the next few weeks, then I will officially release the stable libraries. The gRPC support will then come in a future, likely minor version, release. The OpenAPI extensions may stay in preview as AOT will likely be broken.

Features

All Platforms

  • Support _ prefix character when extracting API versions from a .NET namespace (#​1172)
  • Generate software bill of materials (SBOM) (#​1100)

Fixes

ASP.NET Core with OpenAPI

  • Build-time OpenAPI documents have empty paths (#​1165, #​1168)
  • Missing XML Comments (#​1169)
  • Support <example> tags (#​1170)

Breaking Changes

The OpenAPI extensions for API Versioning (e.g. x-api-versioning) will now use a nested links property rather than a simple array. This allows the schema to be open for possible future enhancements.

Preview 1

{
    "x-api-versioning":
    [
        {
            "title": "Version Policy",
            "type": "text/html",
            "rel": "info",
            "url": "http://my.api.com/policies/versioning.html"
        }
    ]
}

Preview 2+

{
 ... (truncated)

## 10.0.0-preview.1

This is a major release that includes new, publicly visible API changes as well as a rollup of bug fixes. This is an initial preview release that is primarily focused on improving OpenAPI integration. Additional features will come in the next preview. The wiki has not be fully updated - yet, but that will also occur in the near future.

These are preview features and changes. Please report issues if you find them. Feel free to start a [discussion](../../discussions) about the changes in the forthcoming official release.

# Features

## All Platforms

- Support for the `deprecation` response header as defined by [RFC 9745](https://www.rfc-editor.org/rfc/rfc9745.html) (#​1128)

## ASP.NET Core

- Integration with the [Microsoft.AspNetCore.OpenApi](https://www.nuget.org/packages/Microsoft.AspNetCore.OpenApi) library
  - These features in the new [Asp.Versioning.OpenApi](https://www.nuget.org/packages/Asp.Versioning.OpenApi) library
  - OpenAPI documents are now generated per API version
  - Sunset and deprecation policies are automatically included with standard (English) text, but can be customized
  - Sunset and deprecation policies links are included in OpenAPI documents via the `x-api-versioning` extension
  - The versioned `HttpClient` can now read and report on sunset and deprecation policies
  - All [example projects](../../tree/main/examples/AspNetCore) have been updated to use [Scalar](https://scalar.com/)

### Example

The following provides an example of a bare minimum setup:

```c#
var builder = WebApplication.CreateBuilder( args );
var services = builder.Services;

services.AddApiVersioning()
        .AddApiExplorer()
        .AddOpenApi();

var app = builder.Build();
var hello = app.NewVersionedApi( "HelloWorld" );
var v1 = hello.MapGroup( "/hello-world" ).HasApiVersion( 1.0 );
var v2 = hello.MapGroup( "/hello-world" ).HasApiVersion( 2.0 );

v1.MapGet( "/", ( ApiVersion version ) => $"Hello world from v{version}" );
v2.MapGet( "/", ( ApiVersion version ) => $"Hello world from v{version}" );

if ( app.Environment.IsDevelopment() )
{
    app.MapOpenApi().WithDocumentPerVersion();
}

app.Run();

The key differences from what you may be currently doing:

... (truncated)

Commits viewable in compare view.

Updated BCrypt.Net-Next from 4.1.0 to 4.2.0.

Release notes

Sourced from BCrypt.Net-Next's releases.

4.2.0

Full Changelog: BcryptNet/bcrypt.net@v4.1.0...v4.2.0

Commits viewable in compare view.

Updated ErrorOr from 2.0.1 to 2.1.1.

Release notes

Sourced from ErrorOr's releases.

2.1.1

new Release with many new features:

  • Some minor Fixes
  • Support for .NET 8 was added
  • Support for .NET 10 was added
  • Added missing async versions of FailIf methods
  • Added FailIf method overloads that allow to use value in error definition using Func<TValue, Error> error builder
  • Added ElseDo and ElseDoAsync methods
  • Added Else/ElseAsync overloads returning ErrorOr
  • Added Else/ElseAsync overloads returning ErrorOr
  • Added ToErrorOrAsync method
  • Added missing ErrorOrFactory.From methods
  • Added missing collection expression support
  • Added FromAsync and missing ToErrorOrAsync methods
  • Added ThenEnsure and ThenEnsureAsync methods
  • Added IsSuccess property to ErrorOr

Commits viewable in compare view.

Updated Google.Cloud.Storage.V1 from 4.10.0 to 4.14.0.

Release notes

Sourced from Google.Cloud.Storage.V1's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated itext7 from 9.5.0 to 9.6.0.

Release notes

Sourced from itext7's releases.

9.6.0

Our second iText Core release of 2026 will please those with a focus on creating accessible and reusable content in PDF. We’ve introduced the ability for iText to perform automatic color contrast checks during creation of PDF/UA documents, which will aid when ensuring generated documents meet many countries' accessibility regulations.

We’ve also added high-level functionality to make creation of Well Tagged PDF documents easier, by letting iText’s comprehensive conformance checking architecture handle all the tricky stuff behind the scenes. You can also target the reuse and accessibility conformance levels defined in the WTPDF specification, depending on your requirements. The accessibility level directly aligns with PDF/UA-2, while reuse is optimized for content extraction, reflow, and machine-driven transformation.

In addition, we’ve extended trusted list validation to include non‑EU countries, along with general improvements to digital signature validation and certificate retrieval.

PDF/UA Color Contrast Checks

For documents to comply with the PDF/UA specifications, you must ensure that foreground and background colors meet the necessary WCAG standards for accessibility. If there is not enough contrast then not only will documents fail in accessibility checkers, text and graphical content will be difficult to read.

Color contrast checking is something that still requires human intervention in most cases, however, iText Core can now warn you if such issues are detected during document creation. It should be noted that this is not a comprehensive check and cannot substitute for an actual “human in the loop”. However, it will help to identify and avoid obvious issues at an early stage.

This functionality is similar to that provided by the WebAIM Contrast Checker, where you can select different values for the foreground and background colors. For WCAG 2.1 level AA which is commonly specified in accessibility regulations, normal text must have a contrast ratio of at least 4.5:1, and 3:1 for large text, graphics, and user interface components (such as form input borders).

We have also improved iText’s layer handling to better accommodate these tests. Previously, reopening a document and accessing layers via PdfPage.getLayers() always returned layers in the “on” state regardless of their persisted visibility. Now, layer properties are correctly persisted after saving and reopening.

Easier WTPDF Creation

The PDF Association’s Well-Tagged PDF (WTPDF) standard specifies requirements for creating PDF 2.0 documents geared towards reuse and accessibility. While both use cases have a large overlap in requirements, some are critical for reuse while others are only required for accessibility. Therefore the standard has conformance levels that clearly identify the requirements for each.

The reuse level is intended for PDF content to be more easily repurposed, extracted, or reflowed, including use cases such as PDF to HTML conversion and enabling responsive layouts on mobile devices. The accessibility level uses the same structural tagging model, but focuses more on ensuring people using assistive technologies can navigate and understand the document.

WTPDF document creation with iText Core was introduced along with the support for PDF/A-4 and PDF/UA-2, which are both based on the PDF 2.0 specification. However, we’ve since added a comprehensive validation architecture with specialized document classes and validation checkers to enforce compliance when targeting specific standards.

To bring WTPDF into line there is now a dedicated WellTaggedPdfDocument subclass of PdfDocument, to join the existing PdfADocument and PdfUADocument classes. In addition, the PdfConformance class now includes the accessibility and reuse conformance levels.

All these changes mean creating WTPDF documents with iText is just as easy as PDF/A and PDF/UA, with no need to worry about remembering which requirements apply to the conformance level you’re targeting. You can now simply use WellTaggedPdfDocument to create a WTPDF document just like you would use PdfUADocument to create PDF/UA, and let iText do the hard work for you.

Non-EU Trusted List Validation

In iText Core 9.3.0 we introduced the List of Trusted Lists (LOTL) system, which lets iText fetch, validate, and cache European lists for eIDAS compliance. To better accommodate other countries which also issue and maintain trusted lists of their own, we’ve extended the feature to include a broad non‑EU processing implementation.

This was achieved by adding a convenient “single file trust list” alternative implementation path, useful for countries where you have a single XML trust list rather than an EU-style LOTL + pointers ecosystem. The existing LOTL services have been refactored to support this, and the existing Ukraine and Moldova trusted lists samples have been updated to use this new implementation.

You can refer to the Java and .NET sample repositories to find the LOTL validation examples updated for this release.

Improved Digital Signature Validation and Certificate Retrieval

For digital signature validation we’ve introduced a single, configurable mechanism to control all online data retrieval (such as CRL, OCSP, issuing certificates, and LOTL), making it easier to enforce network policies and increase reliability in restricted environments.

Certificate chain building and validation have been updated to better handle complex PKI setups. Chain construction now collects all reachable certificates, including multiple CA candidates and cross-signed certificates, without enforcing constraints during the building phase.

Validation then applies RFC 5280–compliant checks over the resulting paths, with a particular focus on correctly enforcing inherited name constraints across the entire certificate chain. This separation of chain discovery and validation improves robustness and correctness when working with real‑world certificate hierarchies.

Pull Requests

For this release we’d like to thank schallb for their contribution to improve LocationTextExtractionStrategy (Java/.NET) by adding support for custom element and newline separators.

As the author describes, they needed a way to better distinguish between spaces and newlines that are part of the extracted text, and the separators inserted by iText when it decides a word boundary or new line between chunks exists. Thanks to this change, the separators inserted in the formatted extracted text can be overridden.

... (truncated)

Commits viewable in compare view.

Updated itext7.bouncy-castle-adapter from 9.5.0 to 9.6.0.

Updated Microsoft.AspNetCore.Authentication.JwtBearer from 10.0.3 to 10.0.8.

Release notes

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

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.AspNetCore.DataProtection.EntityFrameworkCore from 10.0.3 to 10.0.8.

Release notes

Sourced from Microsoft.AspNetCore.DataProtection.EntityFrameworkCore's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.AspNetCore.SignalR.Client from 10.0.5 to 10.0.8.

Release notes

Sourced from Microsoft.AspNetCore.SignalR.Client's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.EntityFrameworkCore from 10.0.3 to 10.0.8.

Release notes

Sourced from Microsoft.EntityFrameworkCore's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.EntityFrameworkCore.Design from 10.0.3 to 10.0.8.

Release notes

Sourced from Microsoft.EntityFrameworkCore.Design's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated MudBlazor from 9.1.0 to 9.4.0.

Release notes

Sourced from MudBlazor's releases.

9.4.0

What's Changed

Breaking Changes

New Features

Bug Fixes

New Contributors

Full Changelog: MudBlazor/MudBlazor@v9.3.0...v9.4.0

9.3.0

What's Changed

New Features

Bug Fixes

New Contributors

9.2.0

What's Changed

New Features

Bug Fixes

New Contributors

Full Changelog: MudBlazor/MudBlazor@v9.1.0...v9.2.0

Commits viewable in compare view.

Updated Npgsql.EntityFrameworkCore.PostgreSQL from 10.0.0 to 10.0.1.

Release notes

Sourced from Npgsql.EntityFrameworkCore.PostgreSQL's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated SixLabors.ImageSharp from 3.1.12 to 4.0.0.

Release notes

Sourced from SixLabors.ImageSharp's releases.

4.0.0

What's Changed

Commits viewable in compare view.

Updated Swashbuckle.AspNetCore from 6.9.0 to 10.1.7.

Release notes

Sourced from Swashbuckle.AspNetCore's releases.

10.1.7

What's Changed

New Contributors

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.1.6...v10.1.7

10.1.6

What's Changed

New Contributors

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.1.5...v10.1.6

10.1.5

What's Changed

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.1.4...v10.1.5

10.1.4

What's Changed

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.1.3...v10.1.4

10.1.3

What's Changed

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.1.2...v10.1.3

10.1.2

What's Changed

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.1.1...v10.1.2

10.1.1

What's Changed

New Contributors

Full Changelog:

domaindrivendev/Swashbuckle.AspNetCore@v10.1.0...v10.1.1

10.1.0

What's Changed

New Features

Bug Fixes

Miscellaneous

New Contributors

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.0.1...v10.1.0

10.0.1

What's Changed

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.0.0...v10.0.1

10.0.0

Swashbuckle.AspNetCore v10.0.0

[!IMPORTANT]
This release contains major breaking changes.

Read our v10 migration guide for further information.

With this release, Swashbuckle.AspNetCore adds support for generating OpenAPI 3.1 documents and for ASP.NET Core 10.

Swashbuckle.AspNetCore v10 depends on OpenAPI.NET v2.3 which introduces many breaking changes to the public API surface. More information can be found in their OpenAPI.NET v2 Upgrade Guide.

To reduce the number of breaking behavioural changes in Swashbuckle.AspNetCore v10, generation of OpenAPI 3.1 documents is opt-in.
To generate OpenAPI 3.1 documents, change the OpenAPI version as shown in the code snippet below:

app.UseSwagger(options =>
{
    options.OpenApiVersion = OpenApiSpecVersion.OpenApi3_1;
});

[!TIP]
It is strongly recommended that you upgrade to Swashbuckle.AspNetCore v9.0.6 before upgrading to v10.

[!IMPORTANT]
Use of Swashbuckle.AspNetCore with the ASP.NET Core WithOpenApi() method is no longer supported.

What's Changed

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v9.0.6...v10.0.0

9.0.6

What's Changed

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v9.0.5...v9.0.6

9.0.5

What's Changed

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v9.0.4...v9.0.5

9.0.4

What's Changed

New Contributors

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v9.0.3...v9.0.4

9.0.3

What's Changed

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v9.0.2...v9.0.3

9.0.2

What's Changed

New Contributors

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v9.0.1...v9.0.2

9.0.1

What's Changed

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v9.0.0...v9.0.1

9.0.0

📣 This release contains the following breaking changes:

  • Drops support for netstandard2.0 and thus .NET Framework - now only net8.0 and net9.0 are supported.
  • Removes all public members annotated as [Obsolete] in previous releases.
  • Removes the deprecated --serializeasv2 option from Swashbuckle.AspNetCore.Cli, which was superseded by --openapiversion from version 8.0.0.

What's Changed

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v8.1.4...v9.0.0

8.1.4

What's Changed

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v8.1.3...v8.1.4

8.1.3

What's Changed

New Contributors

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v8.1.2...v8.1.3

8.1.2

What's Changed

New Contributors

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v8.1.1...v8.1.2

8.1.1

What's Changed

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v8.1.0...v8.1.1

8.1.0

What's Changed

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v8.0.0...v8.1.0

8.0.0

[!IMPORTANT]
Swashbuckle.AspNetCore drops support for .NET 6.

Swashbuckle.AspNetCore v8.0.0 makes the following notable changes:

  • Drops support for net6.0.
  • The netstandard2.0 TFM now depends on ASP.NET Core 2.3 instead of ASP.NET Core 2.1.
  • Updates Microsoft.OpenApi to v1.6.23. This update requires the use of swagger-ui v5.19.0 or later (v5.20.1 is included in the Swashbuckle.AspNetCore.SwaggerUI NuGet package). You may need to clear your browser's cache to pick up the latest JavaScript files for swagger-ui.
  • To prepare for future support for OpenAPI 3.1 documents, deprecates the SerializeAsV2 property by marking it as [Obsolete]. Users should update their code as illustrated below, depending on their use case: 
    - options.SerializeAsV2 = true;
+ options.Ope....

Description has been truncated

@dependabot
deps: Bump the dotnet-dependencies group with 19 updates
becd64b 
Bumps Asp.Versioning.Mvc from 8.1.0 to 10.0.0
Bumps Asp.Versioning.Mvc.ApiExplorer from 8.1.0 to 10.0.0
Bumps BCrypt.Net-Next from 4.1.0 to 4.2.0
Bumps ErrorOr from 2.0.1 to 2.1.1
Bumps Google.Cloud.Storage.V1 from 4.10.0 to 4.14.0
Bumps itext7 from 9.5.0 to 9.6.0
Bumps itext7.bouncy-castle-adapter from 9.5.0 to 9.6.0
Bumps Microsoft.AspNetCore.Authentication.JwtBearer from 10.0.3 to 10.0.8
Bumps Microsoft.AspNetCore.DataProtection.EntityFrameworkCore from 10.0.3 to 10.0.8
Bumps Microsoft.AspNetCore.SignalR.Client from 10.0.5 to 10.0.8
Bumps Microsoft.EntityFrameworkCore from 10.0.3 to 10.0.8
Bumps Microsoft.EntityFrameworkCore.Design from 10.0.3 to 10.0.8
Bumps MudBlazor from 9.1.0 to 9.4.0
Bumps Npgsql.EntityFrameworkCore.PostgreSQL from 10.0.0 to 10.0.1
Bumps SixLabors.ImageSharp from 3.1.12 to 4.0.0
Bumps Swashbuckle.AspNetCore from 6.9.0 to 10.1.7
Bumps Swashbuckle.AspNetCore.Annotations from 6.9.0 to 10.1.7
Bumps System.Drawing.Common from 10.0.5 to 10.0.8
Bumps System.Management from 10.0.0 to 10.0.8

---
updated-dependencies:
- dependency-name: Asp.Versioning.Mvc
  dependency-version: 10.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: dotnet-dependencies
- dependency-name: Asp.Versioning.Mvc.ApiExplorer
  dependency-version: 10.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: dotnet-dependencies
- dependency-name: BCrypt.Net-Next
  dependency-version: 4.2.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dotnet-dependencies
- dependency-name: BCrypt.Net-Next
  dependency-version: 4.2.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dotnet-dependencies
- dependency-name: ErrorOr
  dependency-version: 2.1.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dotnet-dependencies
- dependency-name: ErrorOr
  dependency-version: 2.1.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dotnet-dependencies
- dependency-name: Google.Cloud.Storage.V1
  dependency-version: 4.14.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dotnet-dependencies
- dependency-name: itext7
  dependency-version: 9.6.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dotnet-dependencies
- dependency-name: itext7.bouncy-castle-adapter
  dependency-version: 9.6.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dotnet-dependencies
- dependency-name: Microsoft.AspNetCore.Authentication.JwtBearer
  dependency-version: 10.0.8
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dotnet-dependencies
- dependency-name: Microsoft.AspNetCore.Authentication.JwtBearer
  dependency-version: 10.0.8
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dotnet-dependencies
- dependency-name: Microsoft.AspNetCore.DataProtection.EntityFrameworkCore
  dependency-version: 10.0.8
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dotnet-dependencies
- dependency-name: Microsoft.AspNetCore.DataProtection.EntityFrameworkCore
  dependency-version: 10.0.8
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dotnet-dependencies
- dependency-name: Microsoft.EntityFrameworkCore
  dependency-version: 10.0.8
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dotnet-dependencies
- dependency-name: Microsoft.AspNetCore.SignalR.Client
  dependency-version: 10.0.8
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dotnet-dependencies
- dependency-name: Microsoft.EntityFrameworkCore.Design
  dependency-version: 10.0.8
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dotnet-dependencies
- dependency-name: Microsoft.EntityFrameworkCore.Design
  dependency-version: 10.0.8
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dotnet-dependencies
- dependency-name: MudBlazor
  dependency-version: 9.4.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dotnet-dependencies
- dependency-name: Npgsql.EntityFrameworkCore.PostgreSQL
  dependency-version: 10.0.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dotnet-dependencies
- dependency-name: Npgsql.EntityFrameworkCore.PostgreSQL
  dependency-version: 10.0.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dotnet-dependencies
- dependency-name: SixLabors.ImageSharp
  dependency-version: 4.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: dotnet-dependencies
- dependency-name: Swashbuckle.AspNetCore
  dependency-version: 10.1.7
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: dotnet-dependencies
- dependency-name: Swashbuckle.AspNetCore.Annotations
  dependency-version: 10.1.7
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: dotnet-dependencies
- dependency-name: System.Drawing.Common
  dependency-version: 10.0.8
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dotnet-dependencies
- dependency-name: System.Management
  dependency-version: 10.0.8
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dotnet-dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github
Copy link
Copy Markdown
Author

dependabot Bot commented on behalf of github May 18, 2026

Labels

The following labels could not be found: dependencies, security. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants