Skip to content

Bump the nuget-deps group with 5 updates - #494

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/main/nuget-deps-7db4bb4f74
Open

Bump the nuget-deps group with 5 updates#494
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/main/nuget-deps-7db4bb4f74

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

Updated Microsoft.Extensions.Logging.Abstractions from 10.0.14 to 11.0.0.

Release notes

Sourced from Microsoft.Extensions.Logging.Abstractions'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.

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

Release notes

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

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.SourceLink.GitHub from 10.0.403 to 11.0.100.

Release notes

Sourced from Microsoft.SourceLink.GitHub's releases.

11.0.100

You can build .NET 11.0 from the repository by cloning the release tag v11.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

Important

Please use https://builds.dotnet.microsoft.com/dotnet/source-build/dotnet-source-11.0.100-rtm.26529.118.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.

11.0.100-rc.3.26522.148

You can build .NET 11.0 RC 3 from the repository by cloning the release tag v11.0.100-rc.3.26522.148 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-11.0.100-rc.3.26522.148.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.

11.0.100-rc.2.26504.105

You can build .NET 11.0 RC 2 from the repository by cloning the release tag v11.0.100-rc.2.26504.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

11.0.100-rc.1.26425.128

You can build .NET 11.0 RC 1 from the repository by cloning the release tag v11.0.100-rc.1.26425.128 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

11.0.100-preview.7.26381.103

You can build .NET 11.0 Preview 7 from the repository by cloning the release tag v11.0.100-preview.7.26381.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 are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

11.0.100-preview.6.26359.118

You can build .NET 11.0 Preview 6 from the repository by cloning the release tag v11.0.100-preview.6.26359.118 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

11.0.100-preview.5.26302.115

You can build .NET 11.0 Preview 5 from the repository by cloning the release tag v11.0.100-preview.5.26302.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

11.0.100-preview.4.26230.115

You can build .NET 11.0 Preview 4 from the repository by cloning the release tag v11.0.100-preview.4.26230.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

11.0.100-preview.3.26207.106

You can build .NET 11.0 Preview 3 from the repository by cloning the release tag v11.0.100-preview.3.26207.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

11.0.100-preview.2.26159.112

You can build .NET 11.0 Preview 2 from the repository by cloning the release tag v11.0.100-preview.2.26159.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

11.0.100-preview.1.26104.118

You can build .NET 11.0 Preview 1 from the repository by cloning the release tag v11.0.100-preview.1.26104.118 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.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.

Commits viewable in compare view.

Updated ptr727.Utilities from 4.1.109 to 4.1.112.

Release notes

Sourced from ptr727.Utilities's releases.

4.1.112

What's Changed

Full Changelog: ptr727/Utilities@4.1.109...4.1.112

Commits viewable in compare view.

Updated System.CommandLine from 2.0.14 to 3.0.0.

Release notes

Sourced from System.CommandLine's releases.

No release notes found for this version range.

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

@dependabot
Bump the nuget-deps group with 5 updates
742502f 
Bumps Microsoft.Extensions.Logging.Abstractions from 10.0.14 to 11.0.0
Bumps Microsoft.NET.Test.Sdk from 18.11.0 to 18.11.1
Bumps Microsoft.SourceLink.GitHub from 10.0.403 to 11.0.100
Bumps ptr727.Utilities from 4.1.109 to 4.1.112
Bumps System.CommandLine from 2.0.14 to 3.0.0

---
updated-dependencies:
- dependency-name: Microsoft.Extensions.Logging.Abstractions
  dependency-version: 11.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: nuget-deps
- dependency-name: Microsoft.NET.Test.Sdk
  dependency-version: 18.11.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-deps
- dependency-name: Microsoft.SourceLink.GitHub
  dependency-version: 11.0.100
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: nuget-deps
- dependency-name: ptr727.Utilities
  dependency-version: 4.1.112
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-deps
- dependency-name: System.CommandLine
  dependency-version: 3.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: nuget-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 11, 2026
@coderabbitai

coderabbitai Bot commented Nov 11, 2026

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@ptr727-codegen
ptr727-codegen Bot enabled auto-merge November 11, 2026 02:45
@codecov

codecov Bot commented Nov 11, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87.68%. Comparing base (4135109) to head (742502f).

Additional details and impacted files 
@@           Coverage Diff           @@
##             main     #494   +/-   ##
=======================================
  Coverage   87.68%   87.68%           
=======================================
  Files          11       11           
  Lines        1941     1941           
  Branches      252      252           
=======================================
  Hits         1702     1702           
  Misses        166      166           
  Partials       73       73
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

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

dependencies Pull requests that update a dependency file .NET Pull requests that update .NET code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants