Repository navigation
chore(deps): update microsoft (major) - #181
Open
Workleap IT (Infra-Workleap) wants to merge 1 commit into
Open
Workleap IT (Infra-Workleap) wants to merge 1 commit into
Workleap IT (Infra-Workleap) wants to merge 1 commit into
Conversation
Workleap IT (Infra-Workleap)
had a problem deploying
to
ci
October 24, 2026 04:48 — with
GitHub Actions
Failure
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
Missing generated analyzer configuration updates cause the build script to stop before packaging and tests.
1 open issue
What changed in this PR
Updates the Microsoft analyzer dependencies distributed with the coding-standards package.
Changes:
- Upgrades BannedApiAnalyzers from
3.3.4to5.6.0. - Upgrades NetAnalyzers from
10.0.401to11.0.100-rc.2.26504.105.
Builds and tests were not run in this review environment.
| File | Description |
|---|---|
Workleap.DotNet.CodingStandards.nuspec |
Updates both Microsoft analyzer dependency versions. |
Review effort: Balanced
| <dependency id="Microsoft.CodeAnalysis.BannedApiAnalyzers" version="3.3.4" /> | ||
| <dependency id="Microsoft.CodeAnalysis.NetAnalyzers" version="10.0.401" /> | ||
| <dependency id="Microsoft.CodeAnalysis.BannedApiAnalyzers" version="5.6.0" /> | ||
| <dependency id="Microsoft.CodeAnalysis.NetAnalyzers" version="11.0.100-rc.2.26504.105" /> |
workleap-renovate
Bot
force-pushed
the
renovate/major-microsoft
branch
from
November 2, 2026 02:02
d005db4 to
995376d
Compare
workleap-renovate
Bot
force-pushed
the
renovate/major-microsoft
branch
from
November 3, 2026 02:13
995376d to
50835c6
Compare
workleap-renovate
Bot
force-pushed
the
renovate/major-microsoft
branch
from
November 18, 2026 02:07
50835c6 to
19bf9a2
Compare
This branch had an error being deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

This PR contains the following updates:
10.0.12→11.0.03.3.4→5.6.010.0.401→11.0.10010.0.14→11.0.0Release Notes
dotnet/dotnet (Microsoft.CodeAnalysis.NetAnalyzers)
v11.0.100: .NET 11.0.0 / 11.0.100Compare Source
You can build .NET 11.0 from the repository by cloning the release tag
v11.0.100and 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 use0:0. The source contents are identical, but the ownership metadata changes the archive bytes, causing signature verification to fail.v11.0.100-rc.3.26522.148: .NET 11.0 RC 3Compare Source
You can build .NET 11.0 RC 3 from the repository by cloning the release tag
v11.0.100-rc.3.26522.148and 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 use0:0. The source contents are identical, but the ownership metadata changes the archive bytes, causing signature verification to fail.v11.0.100-rc.2.26504.105: .NET 11.0 RC 2Compare Source
You can build .NET 11.0 RC 2 from the repository by cloning the release tag
v11.0.100-rc.2.26504.105and 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
v11.0.100-rc.1.26425.128: .NET 11.0 RC 1Compare Source
You can build .NET 11.0 RC 1 from the repository by cloning the release tag
v11.0.100-rc.1.26425.128and 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
v11.0.100-preview.7.26381.103: .NET 11.0 Preview 7Compare Source
You can build .NET 11.0 Preview 7 from the repository by cloning the release tag
v11.0.100-preview.7.26381.103and 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
v11.0.100-preview.6.26359.118: .NET 11.0 Preview 6Compare Source
You can build .NET 11.0 Preview 6 from the repository by cloning the release tag
v11.0.100-preview.6.26359.118and 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
v11.0.100-preview.5.26302.115: .NET 11.0 Preview 5Compare Source
You can build .NET 11.0 Preview 5 from the repository by cloning the release tag
v11.0.100-preview.5.26302.115and 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
v11.0.100-preview.4.26230.115: .NET 11.0 Preview 4Compare Source
You can build .NET 11.0 Preview 4 from the repository by cloning the release tag
v11.0.100-preview.4.26230.115and 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
v11.0.100-preview.3.26207.106: .NET 11.0 Preview 3Compare Source
You can build .NET 11.0 Preview 3 from the repository by cloning the release tag
v11.0.100-preview.3.26207.106and 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
v11.0.100-preview.2.26159.112: .NET 11.0 Preview 2Compare Source
You can build .NET 11.0 Preview 2 from the repository by cloning the release tag
v11.0.100-preview.2.26159.112and 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
v11.0.100-preview.1.26104.118: .NET 11.0 Preview 1Compare Source
You can build .NET 11.0 Preview 1 from the repository by cloning the release tag
v11.0.100-preview.1.26104.118and 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
v10.0.404: .NET 10.0.15 / 10.0.404Compare Source
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.404and 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 use0:0. The source contents are identical, but the ownership metadata changes the archive bytes, causing signature verification to fail.v10.0.403: .NET 10.0.14 / 10.0.403Compare Source
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.403and 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
v10.0.402: .NET 10.0.13 / 10.0.402Compare Source
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.402and 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
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate CLI.