Repository navigation
Update dotnet monorepo to v10 - #604
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
6 times, most recently
from
November 23, 2025 00:48
250244f to
fafa360
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
December 10, 2025 13:07
fafa360 to
e7c2968
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
January 13, 2026 21:45
e7c2968 to
a903d88
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
January 14, 2026 17:14
a903d88 to
89664f0
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
2 times, most recently
from
February 11, 2026 22:06
84655e3 to
73268e9
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
3 times, most recently
from
March 14, 2026 19:42
0ba7f2d to
8244966
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
2 times, most recently
from
April 15, 2026 04:46
af3f0f5 to
169cd62
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
2 times, most recently
from
April 22, 2026 05:59
bd8227e to
35c28d0
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
2 times, most recently
from
May 13, 2026 10:11
d51bacb to
46a14b9
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
June 2, 2026 16:51
46a14b9 to
2b70fa9
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
2 times, most recently
from
June 11, 2026 18:46
8b3c269 to
1cbb847
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
2 times, most recently
from
July 15, 2026 17:53
5fc9f61 to
0c40833
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
August 12, 2026 01:52
0c40833 to
f4d48dc
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
August 28, 2026 22:47
f4d48dc to
b1a092b
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
August 29, 2026 01:52
b1a092b to
23f7f98
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
September 6, 2026 17:55
23f7f98 to
5f2a0e5
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
September 6, 2026 22:15
5f2a0e5 to
58adedc
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
September 8, 2026 11:55
58adedc to
7f482e8
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
September 8, 2026 15:11
7f482e8 to
5d0fc1f
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
2 times, most recently
from
September 9, 2026 01:29
2d4808e to
3d09c7b
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
2 times, most recently
from
October 14, 2026 09:27
8ec78d5 to
7f4aef4
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
October 25, 2026 21:25
7f4aef4 to
c5e7414
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
October 26, 2026 10:58
c5e7414 to
18b070d
Compare
This branch has not been 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.
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
8.0.0→10.0.4039.0.308→10.0.403Release Notes
dotnet/dotnet (Microsoft.SourceLink.GitHub)
v10.0.403: .NET 10.0.14 / 10.0.403You 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.402You 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
v10.0.401: .NET 10.0.12/10.0.401Release
What's Changed
Full Changelog: dotnet/dotnet@v10.0.400...v10.0.401
v10.0.400: .NET 10.0.11 / 10.0.400You can build .NET 10.0 from the repository by cloning the release tag
v10.0.400and 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.303: .NET 10.0.11 / 10.0.303You can build .NET 10.0 from the repository by cloning the release tag
v10.0.303and 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.301: .NET 10.0.9 / 10.0.301You can build .NET 10.0 from the repository by cloning the release tag
v10.0.301and 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.300: .NET 10.0.8 / 10.0.300You can build .NET 10.0 from the repository by cloning the release tag
v10.0.300and 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.204: .NET 10.0.8 / 10.0.204You can build .NET 10.0 from the repository by cloning the release tag
v10.0.204and 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.203: .NET 10.0.7 / 10.0.203You can build .NET 10.0 from the repository by cloning the release tag
v10.0.203and 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.202: .NET 10.0.6 / 10.0.202You can build .NET 10.0 from the repository by cloning the release tag
v10.0.202and 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.201: .NET 10.0.5 / 10.0.201You can build .NET 10.0 from the repository by cloning the release tag
v10.0.201and 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.200: .NET 10.0.4 / 10.0.200You can build .NET 10.0 from the repository by cloning the release tag
v10.0.200and 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.114: .NET 10.0.14 / 10.0.114You can build .NET 10.0 from the repository by cloning the release tag
v10.0.114and 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 use0:0. The source contents are identical, but the ownership metadata changes the archive bytes, causing signature verification to fail.v10.0.113: .NET 10.0.13 / 10.0.113You can build .NET 10.0 from the repository by cloning the release tag
v10.0.113and 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.112: .NET 10.0.12 / 10.0.112You can build .NET 10.0 from the repository by cloning the release tag
v10.0.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
v10.0.111: .NET 10.0.11 / 10.0.111You can build .NET 10.0 from the repository by cloning the release tag
v10.0.111and 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.110: .NET 10.0.10 / 10.0.110You can build .NET 10.0 from the repository by cloning the release tag
v10.0.110and 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.109: .NET 10.0.9 / 10.0.109You can build .NET 10.0 from the repository by cloning the release tag
v10.0.109and 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.108: .NET 10.0.8 / 10.0.108You can build .NET 10.0 from the repository by cloning the release tag
v10.0.108and 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.107: .NET 10.0.7 / 10.0.107You can build .NET 10.0 from the repository by cloning the release tag
v10.0.107and 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.106: .NET 10.0.6 / 10.0.106You can build .NET 10.0 from the repository by cloning the release tag
v10.0.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
v10.0.105: .NET 10.0.5 / 10.0.105You can build .NET 10.0 from the repository by cloning the release tag
v10.0.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
v10.0.104: .NET 10.0.4 / 10.0.104You can build .NET 10.0 from the repository by cloning the release tag
v10.0.104and 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.103: .NET 10.0.3 / 10.0.103You can build .NET 10.0 from the repository by cloning the release tag
v10.0.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 is the PGP signature for the GitHub generated tarball. You can find the public key at https://dot.net/release-key-2023
dotnet/sdk (dotnet-sdk)
v10.0.403Compare Source
v10.0.402: .NET 10.0.13Compare Source
Release
What's Changed
3038879by @dotnet-bot in #55608Full Changelog: dotnet/sdk@v10.0.400...v10.0.402
v10.0.401: .NET 10.0.12Compare Source
Release
What's Changed
dotnet newto suggest@instead of deprecated::separator in update notifications by @marcpopMSFT with @Copilot in #51153Configuration
📅 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.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.