Skip to content

Bump Microsoft.CodeAnalysis.Analyzers and 3 others - #532

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/microsoft-codeanalysis-31b43b6c45
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/microsoft-codeanalysis-31b43b6c45

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Updated Microsoft.CodeAnalysis.Analyzers from 5.6.0 to 5.12.0.

Release notes

Sourced from Microsoft.CodeAnalysis.Analyzers's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.CodeAnalysis.CSharp from 5.6.0 to 5.12.0.

Release notes

Sourced from Microsoft.CodeAnalysis.CSharp's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.CodeAnalysis.CSharp.Workspaces from 5.6.0 to 5.12.0.

Updated Microsoft.CodeAnalysis.NetAnalyzers from 10.0.302 to 11.0.100.

Release notes

Sourced from Microsoft.CodeAnalysis.NetAnalyzers'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.

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

Commits viewable in compare view.

@dependabot dependabot Bot added .NET Pull requests that update .net code dependencies Pull requests that update a dependency file labels Nov 16, 2026
@github-actions
github-actions Bot enabled auto-merge (squash) November 16, 2026 16:16
Bumps Microsoft.CodeAnalysis.Analyzers from 5.6.0 to 5.12.0
Bumps Microsoft.CodeAnalysis.CSharp from 5.6.0 to 5.12.0
Bumps Microsoft.CodeAnalysis.CSharp.Workspaces from 5.6.0 to 5.12.0
Bumps Microsoft.CodeAnalysis.NetAnalyzers from 10.0.302 to 11.0.100

---
updated-dependencies:
- dependency-name: Microsoft.CodeAnalysis.Analyzers
  dependency-version: 5.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: microsoft-codeanalysis
- dependency-name: Microsoft.CodeAnalysis.CSharp
  dependency-version: 5.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: microsoft-codeanalysis
- dependency-name: Microsoft.CodeAnalysis.CSharp.Workspaces
  dependency-version: 5.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: microsoft-codeanalysis
- dependency-name: Microsoft.CodeAnalysis.NetAnalyzers
  dependency-version: 11.0.100
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: microsoft-codeanalysis
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title Bump the microsoft-codeanalysis group with 4 updates Bump Microsoft.CodeAnalysis.Analyzers and 3 others Nov 16, 2026
@dependabot
dependabot Bot force-pushed the dependabot/nuget/microsoft-codeanalysis-31b43b6c45 branch from c5f2252 to 5d7b7b5 Compare November 16, 2026 16:28

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