Skip to content

(PATCH): Bump Microsoft.AspNetCore.OpenApi and 8 others - #173

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/PTrampert.SimplePatch.OpenApi.Test/csharp-deps-be9945fcfa
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/PTrampert.SimplePatch.OpenApi.Test/csharp-deps-be9945fcfa

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

Updated Microsoft.AspNetCore.OpenApi from 10.0.14 to 10.0.15.

Release notes

Sourced from Microsoft.AspNetCore.OpenApi's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.NET.Test.Sdk from 18.10.1 to 18.12.0.

Release notes

Sourced from Microsoft.NET.Test.Sdk's releases.

18.12.0

Security fix

This release includes the fix for CVE-2026-105544, an elevation of privilege vulnerability in the VSTest artifact post-processor. The post-processor could consume a forged executionComplete.json written by another local user, and then run attacker-controlled output handling.

Affected: Microsoft.TestPlatform.CLI 18.11.0 and earlier. Every version from 18.11.1 on is fixed, including 18.12.0.

Microsoft.TestPlatform.CLI is the VSTest build that we ship into the .NET SDK. The recommended way to get this fix is to update your .NET SDK to the latest patched version, see the advisory for the SDK versions.

The fix is also released in the Microsoft.TestPlatform.CLI package, for completeness. That package is rarely used directly. It is not a dependency of Microsoft.NET.Test.Sdk or Microsoft.TestPlatform, so those packages do not bring it in.

Details: microsoft/vstest#16654 and dotnet/announcements#517

Using custom Docker images or Nano Server? See microsoft/vstest#16652

What's Changed

Full Changelog: microsoft/vstest@v18.11.0...v18.12.0

18.11.1

Security fix

This release fixes CVE-2026-105544, an elevation of privilege vulnerability in the VSTest artifact post-processor. The post-processor could consume a forged executionComplete.json written by another local user, and then run attacker-controlled output handling.

Affected: Microsoft.TestPlatform.CLI 18.11.0.
Fixed in: Microsoft.TestPlatform.CLI 18.11.1.

Microsoft.TestPlatform.CLI is the VSTest build that we ship into the .NET SDK. The recommended way to get this fix is to update your .NET SDK to the latest patched version, see the advisory for the SDK versions.

The fix is also released in the Microsoft.TestPlatform.CLI package, for completeness. That package is rarely used directly. It is not a dependency of Microsoft.NET.Test.Sdk or Microsoft.TestPlatform, so those packages do not bring it in.

Details: microsoft/vstest#16654 and dotnet/announcements#517

Using custom Docker images or Nano Server? See microsoft/vstest#16652

What's Changed

Full Changelog: microsoft/vstest@v18.11.0...v18.11.1

18.11.0

What's Changed

New Contributors

Full Changelog: microsoft/vstest@v18.10.1...v18.11.0

18.10.2

Security fix

This release fixes CVE-2026-105544, an elevation of privilege vulnerability in the VSTest artifact post-processor. The post-processor could consume a forged executionComplete.json written by another local user, and then run attacker-controlled output handling.

Affected: Microsoft.TestPlatform.CLI 18.10.0 and 18.10.1.
Fixed in: Microsoft.TestPlatform.CLI 18.10.2.

Microsoft.TestPlatform.CLI is the VSTest build that we ship into the .NET SDK. The recommended way to get this fix is to update your .NET SDK to the latest patched version, see the advisory for the SDK versions.

The fix is also released in the Microsoft.TestPlatform.CLI package, for completeness. That package is rarely used directly. It is not a dependency of Microsoft.NET.Test.Sdk or Microsoft.TestPlatform, so those packages do not bring it in.

Details: microsoft/vstest#16654 and dotnet/announcements#517

Using custom Docker images or Nano Server? See microsoft/vstest#16652

What's Changed

Full Changelog: microsoft/vstest@v18.10.1...v18.10.2

Commits viewable in compare view.

Updated Microsoft.NET.Test.Sdk from 18.11.0 to 18.12.0.

Release notes

Sourced from Microsoft.NET.Test.Sdk's releases.

18.12.0

Security fix

This release includes the fix for CVE-2026-105544, an elevation of privilege vulnerability in the VSTest artifact post-processor. The post-processor could consume a forged executionComplete.json written by another local user, and then run attacker-controlled output handling.

Affected: Microsoft.TestPlatform.CLI 18.11.0 and earlier. Every version from 18.11.1 on is fixed, including 18.12.0.

Microsoft.TestPlatform.CLI is the VSTest build that we ship into the .NET SDK. The recommended way to get this fix is to update your .NET SDK to the latest patched version, see the advisory for the SDK versions.

The fix is also released in the Microsoft.TestPlatform.CLI package, for completeness. That package is rarely used directly. It is not a dependency of Microsoft.NET.Test.Sdk or Microsoft.TestPlatform, so those packages do not bring it in.

Details: microsoft/vstest#16654 and dotnet/announcements#517

Using custom Docker images or Nano Server? See microsoft/vstest#16652

What's Changed

Full Changelog: microsoft/vstest@v18.11.0...v18.12.0

18.11.1

Security fix

This release fixes CVE-2026-105544, an elevation of privilege vulnerability in the VSTest artifact post-processor. The post-processor could consume a forged executionComplete.json written by another local user, and then run attacker-controlled output handling.

Affected: Microsoft.TestPlatform.CLI 18.11.0.
Fixed in: Microsoft.TestPlatform.CLI 18.11.1.

Microsoft.TestPlatform.CLI is the VSTest build that we ship into the .NET SDK. The recommended way to get this fix is to update your .NET SDK to the latest patched version, see the advisory for the SDK versions.

The fix is also released in the Microsoft.TestPlatform.CLI package, for completeness. That package is rarely used directly. It is not a dependency of Microsoft.NET.Test.Sdk or Microsoft.TestPlatform, so those packages do not bring it in.

Details: microsoft/vstest#16654 and dotnet/announcements#517

Using custom Docker images or Nano Server? See microsoft/vstest#16652

What's Changed

Full Changelog: microsoft/vstest@v18.11.0...v18.11.1

Commits viewable in compare view.

Pinned Microsoft.OpenApi at 2.13.1.

Release notes

Sourced from Microsoft.OpenApi's releases.

2.13.1

2.13.1 (2026-11-16)

Bug Fixes

  • models: preserve specification extensions in OpenApiPaths and OpenApiResponses copy constructors (#​3162) (#​3163) (3301ba7)
  • models: preserve tag collection types and comparers in copy constructors (#​3141) (#​3145) (aa5e2b5)
  • models: preserve tag collection types and comparers in OpenApiDocument copy constructor (aa5e2b5)
  • reader: backport external reference file loading to v2 (#​3174) (cb3003a)
  • reader: backport external reference loading to v2 (cb3003a)
  • Support custom tag ordering and null assignment in OpenApiOperation.Tags (#​3128) (#​3133) (295c89c)
  • support reinitializing OpenApiOperation.Tags to null and custom comparers (#​3116) (#​3142) (9cfcdd2)
  • v2: map OpenAPI 2.0 response schema type file to binary format (#​3150) (#​3151) (4cf52e1)
  • v3: retain full JSON pointer path on OpenAPI 3.0 schema references (#​3155) (#​3170) (16969bc)

2.13.0

2.13.0 (2026-10-19)

Features

Bug Fixes

Commits viewable in compare view.

Pinned Microsoft.OpenApi at 3.11.1.

Release notes

Sourced from Microsoft.OpenApi's releases.

3.11.1

3.11.1 (2026-11-16)

Bug Fixes

  • improved external ref file loading (#​3164) (a4a4de6)
  • models: preserve specification extensions in OpenApiPaths and OpenApiResponses copy constructors (#​3162) (a68f8be)
  • models: preserve tag collection types and comparers in copy constructors (#​3141) (76ea786)
  • models: preserve tag collection types and comparers in OpenApiDocument copy constructor (76ea786)
  • reader: reduce reference parsing memory allocations (#​3171) (d14d0a1)
  • Support custom tag ordering and null assignment in OpenApiOperation.Tags (#​3128) (d868431)
  • support reinitializing OpenApiOperation.Tags to null and custom comparers (#​3116) (4f53ad5)
  • v2: map OpenAPI 2.0 response schema type file to binary format (#​3150) (e41f0e8)
  • v3: retain full JSON pointer path on OpenAPI 3.0 schema references (#​3155) (d8f20e8)
  • validations: include properties segment in ValidateSchemaPropertyHasValue pointer (#​3165) (4d59cb0)

Commits viewable in compare view.

Updated NUnit from 4.6.1 to 5.0.0.

Release notes

Sourced from NUnit's releases.

5.0.0

See release notes for details.

Commits viewable in compare view.

Updated NUnit.Analyzers from 4.14.0 to 4.15.0.

Release notes

Sourced from NUnit.Analyzers's releases.

4.15.0

NUnit Analyzers 4.15 - September 12, 2026

This release of the NUnit Analyzers adds support for the new numeric types that will
be supported in NUnit 5. The release also improves NUnit1027 by inspecting base fixtures,
and NUnit1028 by supporting IAsyncDisposable.DisposeAsync in addition to the
existing IDisposable.Dispose. The release also includes bug fixes and dependency updates.

The release contains contributions from the following users (in alphabetical order):

  • @​jhavlicek-profinit
  • @​killergege
  • @​manfred-brands
  • @​mikkelbu
  • @​ngbrown
  • @​ramonsmits
  • @​stevenaw
  • @​uladz-zubrycki

Issues Resolved

Features and Enhancements

  • #​1019 NUnit1027 does not see [CancelAfter] inherited from a base fixture
  • #​1017 NU2047 reports failure for new numeric types
  • #​1001 NUnit1028: Allow DisposeAsync as an exception
  • #​999 [TestCaseSource] CA1812 suppression

Bugs

  • #​1013 Use of records crash the NonNullableFieldOrPropertyIsUninitializedSuppressor analyzer
  • #​998 Assert.EnterMultipleScope clears nullability suppress info

Tooling, Process, and Documentation

  • #​1005 Bump Microsoft.NET.Test.Sdk from 18.6.0 to 18.7.0
  • #​996 Bump Microsoft.NET.Test.Sdk from 17.14.1 to 18.6.0
  • #​993 chore: bump version

Commits viewable in compare view.

Updated NUnit3TestAdapter from 6.3.0 to 6.3.1.

Release notes

Sourced from NUnit3TestAdapter's releases.

6.3.1

This is a hotfix release for issue 1504

Commits viewable in compare view.

Updated Swashbuckle.AspNetCore from 10.3.1 to 11.0.1.

Release notes

Sourced from Swashbuckle.AspNetCore's releases.

11.0.1

What's Changed

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

11.0.0

Swashbuckle.AspNetCore v11.0.0

[!IMPORTANT]
This release contains major breaking changes.

Read our v11 migration guide for further information.

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

Swashbuckle.AspNetCore v11 depends on OpenAPI.NET v3.11 which introduces some breaking changes to the public API surface. More information can be found in their OpenAPI.NET v3 Upgrade Guide.

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

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

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

What's Changed

New Contributors

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.3.1...v11.0.0

Commits viewable in compare view.

Updated Swashbuckle.AspNetCore.SwaggerGen from 10.3.1 to 11.0.1.

Release notes

Sourced from Swashbuckle.AspNetCore.SwaggerGen's releases.

11.0.1

What's Changed

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

11.0.0

Swashbuckle.AspNetCore v11.0.0

[!IMPORTANT]
This release contains major breaking changes.

Read our v11 migration guide for further information.

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

Swashbuckle.AspNetCore v11 depends on OpenAPI.NET v3.11 which introduces some breaking changes to the public API surface. More information can be found in their OpenAPI.NET v3 Upgrade Guide.

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

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

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

What's Changed

New Contributors

Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.3.1...v11.0.0

Commits viewable in compare view.

Updated System.CodeDom from 10.0.14 to 11.0.0.

Release notes

Sourced from System.CodeDom's releases.

10.0.404

You can build .NET 10.0 from the repository by cloning the release tag v10.0.404 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

Important

Please use https://builds.dotnet.microsoft.com/dotnet/source-build/dotnet-source-10.0.404-servicing.26529.119.tar.gz instead of the GitHub-generated sources tarball. This is due to a discrepancy in the ownership metadata. The signatures were generated from build-produced source archives with ownership normalized to UID/GID 2001:2001, while GitHub’s automatically generated archives use 0:0. The source contents are identical, but the ownership metadata changes the archive bytes, causing signature verification to fail.

10.0.403

You can build .NET 10.0 from the repository by cloning the release tag v10.0.403 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.402

You can build .NET 10.0 from the repository by cloning the release tag v10.0.402 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.401

Release

What's Changed

... (truncated)

10.0.400

You can build .NET 10.0 from the repository by cloning the release tag v10.0.400 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.303

You can build .NET 10.0 from the repository by cloning the release tag v10.0.303 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.302

You can build .NET 10.0 from the repository by cloning the release tag v10.0.302 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.301

You can build .NET 10.0 from the repository by cloning the release tag v10.0.301 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.300

You can build .NET 10.0 from the repository by cloning the release tag v10.0.300 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.204

You can build .NET 10.0 from the repository by cloning the release tag v10.0.204 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.203

You can build .NET 10.0 from the repository by cloning the release tag v10.0.203 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.202

You can build .NET 10.0 from the repository by cloning the release tag v10.0.202 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.201

You can build .NET 10.0 from the repository by cloning the release tag v10.0.201 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.200

You can build .NET 10.0 from the repository by cloning the release tag v10.0.200 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.115

You can build .NET 10.0 from the repository by cloning the release tag v10.0.115 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

Important

Please use https://builds.dotnet.microsoft.com/dotnet/source-build/dotnet-source-10.0.115-servicing.26529.108.tar.gz instead of the GitHub-generated sources tarball. This is due to a discrepancy in the ownership metadata. The signature was generated from a build-produced source archive with ownership normalized to UID/GID 2001:2001, while GitHub’s automatically generated archive uses 0:0. The source contents are identical, but the ownership metadata changes the archive bytes, causing signature verification to fail.

10.0.114

You can build .NET 10.0 from the repository by cloning the release tag v10.0.114 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

Important

Please use https://builds.dotnet.microsoft.com/dotnet/source-build/dotnet-source-10.0.114-servicing.26522.126.tar.gz instead of the GitHub-generated sources tarball. This is due to a discrepancy in the ownership metadata. The signatures were generated from build-produced source archives with ownership normalized to UID/GID 2001:2001, while GitHub’s automatically generated archives use 0:0. The source contents are identical, but the ownership metadata changes the archive bytes, causing signature verification to fail.

10.0.113

You can build .NET 10.0 from the repository by cloning the release tag v10.0.113 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.112

You can build .NET 10.0 from the repository by cloning the release tag v10.0.112 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.111

You can build .NET 10.0 from the repository by cloning the release tag v10.0.111 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.110

You can build .NET 10.0 from the repository by cloning the release tag v10.0.110 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.109

You can build .NET 10.0 from the repository by cloning the release tag v10.0.109 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.108

You can build .NET 10.0 from the repository by cloning the release tag v10.0.108 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.107

You can build .NET 10.0 from the repository by cloning the release tag v10.0.107 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.106

You can build .NET 10.0 from the repository by cloning the release tag v10.0.106 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.105

You can build .NET 10.0 from the repository by cloning the release tag v10.0.105 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.104

You can build .NET 10.0 from the repository by cloning the release tag v10.0.104 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.103

You can build .NET 10.0 from the repository by cloning the release tag v10.0.103 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached is the PGP signature for the GitHub generated tarball. You can find the public key at https://dot.net/release-key-2023

10.0.102-sb1

You can build .NET 10.0 from the repository by cloning the release tag v10.0.102-sb1 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.101

You can build .NET 10.0 from the repository by cloning the release tag v10.0.101 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.100

You can build .NET 10.0 from the repository by cloning the release tag v10.0.100 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

To produce artifacts with the .NET 10 GA version strings, users must pass the branding argument to the build: --branding rtm.

10.0.100-rc.2.25502.107

You can build .NET 10.0 RC 2 from the repository by cloning the release tag v10.0.100-rc.2.25502.107 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

Note: GitHub automatically generates the "Source code (tar.gz/zip)" archives included in this release. Please download the official source code from:

10.0.100-rc.1.25451.107

You can build .NET 10.0 RC 1 from the repository by cloning the release tag v10.0.100-rc.1.25451.107 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.100-preview.7.25380.108

You can build .NET 10.0 Preview 7 from the repository by cloning the release tag v10.0.100-preview.7.25380.108 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

Commits viewable in compare view.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Bumps Microsoft.AspNetCore.OpenApi from 10.0.14 to 10.0.15
Bumps Microsoft.NET.Test.Sdk to 18.12.0
Bumps Microsoft.OpenApi to 2.13.1, 3.11.1
Bumps NUnit from 4.6.1 to 5.0.0
Bumps NUnit.Analyzers from 4.14.0 to 4.15.0
Bumps NUnit3TestAdapter from 6.3.0 to 6.3.1
Bumps Swashbuckle.AspNetCore from 10.3.1 to 11.0.1
Bumps Swashbuckle.AspNetCore.SwaggerGen from 10.3.1 to 11.0.1
Bumps System.CodeDom from 10.0.14 to 11.0.0

---
updated-dependencies:
- dependency-name: System.CodeDom
  dependency-version: 11.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: csharp-deps
- dependency-name: Microsoft.AspNetCore.OpenApi
  dependency-version: 10.0.15
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: csharp-deps
- dependency-name: Microsoft.OpenApi
  dependency-version: 2.13.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: csharp-deps
- dependency-name: Microsoft.NET.Test.Sdk
  dependency-version: 18.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: csharp-deps
- dependency-name: NUnit
  dependency-version: 5.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: csharp-deps
- dependency-name: NUnit.Analyzers
  dependency-version: 4.15.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: csharp-deps
- dependency-name: NUnit3TestAdapter
  dependency-version: 6.3.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: csharp-deps
- dependency-name: Swashbuckle.AspNetCore
  dependency-version: 11.0.1
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: csharp-deps
- dependency-name: Swashbuckle.AspNetCore.SwaggerGen
  dependency-version: 11.0.1
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: csharp-deps
- dependency-name: Microsoft.OpenApi
  dependency-version: 3.11.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: csharp-deps
- dependency-name: Microsoft.NET.Test.Sdk
  dependency-version: 18.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: csharp-deps
- dependency-name: Microsoft.NET.Test.Sdk
  dependency-version: 18.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: csharp-deps
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added .NET Pull requests that update .NET code dependencies Pull requests that update a dependency file labels Nov 18, 2026
@github-actions

Copy link
Copy Markdown

✅ PR Title Formatted Correctly

The title of this PR has been updated to match the correct format. Thank you!

This branch has not been deployed

No deployments
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