Skip to content

Update dotnet monorepo to v10 - #320

Open
renovate[bot] wants to merge 1 commit into
developfrom
renovate/major-dotnet-monorepo
Open

Update dotnet monorepo to v10#320
renovate[bot] wants to merge 1 commit into
developfrom
renovate/major-dotnet-monorepo

Conversation

@renovate

@renovate renovate Bot commented Nov 12, 2025 •
edited
Loading

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Type Update
Microsoft.SourceLink.GitHub 8.0.0 → 10.0.403 age confidence nuget major
dotnet-sdk 9.0.306 → 10.0.403 age confidence dotnet-sdk major
dotnet-sdk 7.0.x → 10.0.x age confidence uses-with major

Release Notes

dotnet/dotnet (Microsoft.SourceLink.GitHub)

v10.0.403: .NET 10.0.14 / 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

v10.0.402: .NET 10.0.13 / 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

v10.0.401: .NET 10.0.12/10.0.401

Release

What's Changed

Full Changelog: dotnet/dotnet@v10.0.400...v10.0.401

v10.0.400: .NET 10.0.11 / 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

v10.0.303: .NET 10.0.11 / 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

v10.0.301: .NET 10.0.9 / 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

v10.0.300: .NET 10.0.8 / 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

v10.0.204: .NET 10.0.8 / 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

v10.0.203: .NET 10.0.7 / 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

v10.0.202: .NET 10.0.6 / 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

v10.0.201: .NET 10.0.5 / 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

v10.0.200: .NET 10.0.4 / 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

v10.0.114: .NET 10.0.14 / 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.

v10.0.113: .NET 10.0.13 / 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

v10.0.112: .NET 10.0.12 / 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

v10.0.111: .NET 10.0.11 / 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

v10.0.110: .NET 10.0.10 / 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

v10.0.109: .NET 10.0.9 / 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

v10.0.108: .NET 10.0.8 / 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

v10.0.107: .NET 10.0.7 / 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

v10.0.106: .NET 10.0.6 / 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

v10.0.105: .NET 10.0.5 / 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

v10.0.104: .NET 10.0.4 / 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

v10.0.103: .NET 10.0.3 / 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

dotnet/sdk (dotnet-sdk)

v10.0.403

Compare Source

v10.0.402: .NET 10.0.13

Compare Source

Release

What's Changed

Full Changelog: dotnet/sdk@v10.0.400...v10.0.402

v10.0.401: .NET 10.0.12

Compare Source

Release

What's Changed

[!IMPORTANT]
✂ PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the dependencies Pull requests that update a dependency file label Nov 12, 2025
@renovate
renovate Bot force-pushed the renovate/major-dotnet-monorepo branch from 6b8203b to 117ce7e Compare December 10, 2025 14:10
@renovate
renovate Bot force-pushed the renovate/major-dotnet-monorepo branch from 117ce7e to 1bc2482 Compare January 13, 2026 20:30
@renovate renovate Bot changed the title Update dependency dotnet-sdk to v10 Update dotnet monorepo to v10 (major) Jan 13, 2026
@renovate
renovate Bot force-pushed the renovate/major-dotnet-monorepo branch from 1bc2482 to 87577dd Compare January 14, 2026 18:58
@renovate
renovate Bot force-pushed the renovate/major-dotnet-monorepo branch 2 times, most recently from fbe8265 to 7ca64b5 Compare February 11, 2026 22:35
@renovate
renovate Bot force-pushed the renovate/major-dotnet-monorepo branch 4 times, most recently from f079288 to 0a98f20 Compare March 13, 2026 00:47
@renovate
renovate Bot force-pushed the renovate/major-dotnet-monorepo branch 2 times, most recently from e31ceff to cd9745c Compare April 15, 2026 05:44
@renovate
renovate Bot force-pushed the renovate/major-dotnet-monorepo branch 2 times, most recently from 71cdd37 to 4318396 Compare April 22, 2026 08:10
@renovate renovate Bot changed the title Update dotnet monorepo to v10 (major) Update dotnet monorepo to v10 May 12, 2026
@renovate
renovate Bot force-pushed the renovate/major-dotnet-monorepo branch 2 times, most recently from c09dd7d to c7c89fb Compare May 13, 2026 09:47
@renovate
renovate Bot force-pushed the renovate/major-dotnet-monorepo branch from c7c89fb to bf64466 Compare June 2, 2026 16:37
@renovate
renovate Bot force-pushed the renovate/major-dotnet-monorepo branch 2 times, most recently from 6e5b6bd to a9a224f Compare June 11, 2026 16:36
@renovate
renovate Bot force-pushed the renovate/major-dotnet-monorepo branch 2 times, most recently from 81c7093 to c31c620 Compare July 15, 2026 19:43
@renovate
renovate Bot force-pushed the renovate/major-dotnet-monorepo branch from c31c620 to fd7c9bd Compare August 11, 2026 23:33
@renovate
renovate Bot force-pushed the renovate/major-dotnet-monorepo branch 3 times, most recently from 3d75af8 to e973906 Compare September 15, 2026 17:53
@renovate
renovate Bot force-pushed the renovate/major-dotnet-monorepo branch from e973906 to 9541332 Compare September 16, 2026 18:11
@renovate
renovate Bot force-pushed the renovate/major-dotnet-monorepo branch 2 times, most recently from 69e6a39 to a407180 Compare October 14, 2026 10:03
@renovate
renovate Bot force-pushed the renovate/major-dotnet-monorepo branch from a407180 to e3aeeba Compare October 25, 2026 21:31
@renovate
renovate Bot force-pushed the renovate/major-dotnet-monorepo branch from e3aeeba to 54e6c6d Compare October 26, 2026 11:56

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

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@LordFedri