Repository navigation
chore(deps): update dotnet monorepo to v10 - #384
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
2 times, most recently
from
November 12, 2025 14:04
98f8f63 to
d855e63
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
2 times, most recently
from
December 10, 2025 12:57
c43dc76 to
772d8e6
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
2 times, most recently
from
January 14, 2026 17:25
0a0f83e to
88887ff
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
February 2, 2026 20:43
88887ff to
0a3c6d3
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
2 times, most recently
from
February 11, 2026 21:03
4573c4d to
931c9cc
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
February 24, 2026 17:27
931c9cc to
c2f00c9
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
4 times, most recently
from
March 13, 2026 01:02
3f9dea7 to
44e5473
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
April 7, 2026 13:34
44e5473 to
4d6dd36
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
3 times, most recently
from
April 22, 2026 05:35
23cf89d to
ce3e440
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
April 28, 2026 20:38
ce3e440 to
2dd26f5
Compare
📝 WalkthroughWalkthroughUpdates .NET SDK version from 9.0.306 to 10.0.203 in global.json and bumps two Microsoft.Extensions NuGet packages from 9.0.11 to 10.0.7 in the test project, keeping the SDK rollForward setting unchanged. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related issues
Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
tests/BlazorApplicationInsights.Tests/BlazorApplicationInsights.Tests.csproj (1)
4-4:⚠️ Potential issue | 🟠 MajorUpdate TargetFramework to net10.0 to align with SDK and package versions.
The test project still targets
net9.0, but this PR updates the .NET SDK to 10.0.203 and upgrades Microsoft.Extensions packages to version 10.0.7 (which are .NET 10 packages). This version mismatch may cause compatibility issues, runtime errors, or prevent the project from utilizing .NET 10-specific features properly.🔧 Proposed fix to update TargetFramework
- <TargetFramework>net9.0</TargetFramework> + <TargetFramework>net10.0</TargetFramework>🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@tests/BlazorApplicationInsights.Tests/BlazorApplicationInsights.Tests.csproj` at line 4, Update the test project's TargetFramework XML element from net9.0 to net10.0 to match the updated .NET SDK and package versions; locate the TargetFramework element in the test project file (the <TargetFramework> element) and change its value to "net10.0", then restore/build to ensure compatibility with the upgraded Microsoft.Extensions packages.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Outside diff comments:
In
`@tests/BlazorApplicationInsights.Tests/BlazorApplicationInsights.Tests.csproj`:
- Line 4: Update the test project's TargetFramework XML element from net9.0 to
net10.0 to match the updated .NET SDK and package versions; locate the
TargetFramework element in the test project file (the <TargetFramework> element)
and change its value to "net10.0", then restore/build to ensure compatibility
with the upgraded Microsoft.Extensions packages.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 6f628544-c7e4-4911-aa31-9314616df2ae
📒 Files selected for processing (2)
global.jsontests/BlazorApplicationInsights.Tests/BlazorApplicationInsights.Tests.csproj
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
3 times, most recently
from
May 13, 2026 09:09
9603e5a to
e5eb9aa
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
2 times, most recently
from
June 2, 2026 19:02
5d4f59b to
06268db
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
June 13, 2026 20:02
06268db to
936361b
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
June 23, 2026 13:52
936361b to
bfd2d70
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
3 times, most recently
from
July 15, 2026 16:13
4642abe to
5efdc6e
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
August 11, 2026 23:39
5efdc6e to
197b0f8
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
17 times, most recently
from
September 9, 2026 01:02
9af57f2 to
c66d85b
Compare
renovate
Bot
force-pushed
the
renovate/major-dotnet-monorepo
branch
from
September 9, 2026 05:11
c66d85b to
6577c74
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
1 participant
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:
8.0.*→10.0.1*9.0.*→10.0.1*8.0.*→10.0.1*9.0.*→10.0.1*9.0.*→10.0.1*8.0.*→10.0.1*8.0.*→10.0.1*9.0.*→10.0.1*9.0.11→10.0.129.0.11→10.0.128.0.*→10.0.1*9.0.*→10.0.1*9.0.306→10.0.401Release Notes
dotnet/dotnet (Microsoft.AspNetCore.Components)
v10.0.12v10.0.11v10.0.10v10.0.9v10.0.8v10.0.7v10.0.6v10.0.5v10.0.4v10.0.3v10.0.2v10.0.1v9.0.7: .NET 9.0.7You can build .NET 9.0 from the repository by cloning the release tag
v9.0.7and 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
v9.0.6: .NET 9.0.6You can build .NET 9.0 from the repository by cloning the release tag
v9.0.6and 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
v9.0.5: .NET 9.0.5You can build .NET 9.0 from the repository by cloning the release tag
v9.0.5and 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
v9.0.4: .NET 9.0.4You can build .NET 9.0 from the repository by cloning the release tag
v9.0.4and 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
v9.0.3: .NET 9.0.3You can build .NET 9.0 from the repository by cloning the release tag
v9.0.3and 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
v9.0.2: .NET 9.0.2You can build .NET 9.0 from the repository by cloning the release tag
v9.0.2and 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
v9.0.1: .NET 9.0.1You can build .NET 9.0 from the repository by cloning the release tag
v9.0.1and 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
v9.0.0: .NET 9.0.0You can build .NET 9.0 from the repository by cloning the release tag
v9.0.0and 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
v8.0.18: .NET 8.0.18You can build .NET 8.0 from the repository by cloning the release tag
v8.0.18and 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
v8.0.17: .NET 8.0.17You can build .NET 8.0 from the repository by cloning the release tag
v8.0.17and 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
v8.0.16: .NET 8.0.16You can build .NET 8.0 from the repository by cloning the release tag
v8.0.16and 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
v8.0.15: .NET 8.0.15You can build .NET 8.0 from the repository by cloning the release tag
v8.0.15and 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
v8.0.14: .NET 8.0.14You can build .NET 8.0 from the repository by cloning the release tag
v8.0.14and 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
v8.0.13: .NET 8.0.13You can build .NET 8.0 from the repository by cloning the release tag
v8.0.13and 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
v8.0.12: .NET 8.0.12You can build .NET 8.0 from the repository by cloning the release tag
v8.0.12and 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
v8.0.11: .NET 8.0.11You can build .NET 8.0 from the repository by cloning the release tag
v8.0.11and 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
v8.0.10: .NET 8.0.10You can build .NET 8.0 from the repository by cloning the release tag
v8.0.10and 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
v8.0.8: .NET 8.0.8You can build .NET 8.0 from the repository by cloning the release tag
v8.0.8and 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
v8.0.7: .NET 8.0.7You can build .NET 8.0 from the repository by cloning the release tag
v8.0.7and 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
v8.0.6: .NET 8.0.6You can build .NET 8.0 from the repository by cloning the release tag
v8.0.6and 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
v8.0.5: .NET 8.0.5You can build .NET 8 from the repository by cloning the release tag
v8.0.5and 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
v8.0.4: .NET 8.0.4You can build .NET 8.0 from the repository by cloning the release tag
v8.0.4and 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
v8.0.3: .NET 8.0.3You can build .NET 8.0 from the repository by cloning the release tag
v8.0.3and 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
v8.0.2: .NET 8.0.2You can build .NET 8.0 from the repository by cloning the release tag
v8.0.2and 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
v8.0.1: .NET 8.0.1You can build .NET 8.0 from the repository by cloning the release tag
v8.0.1and 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://dotnet.microsoft.com/download/dotnet/release-key-2023.asc
dotnet/sdk (dotnet-sdk)
v10.0.401Compare Source
v10.0.400Compare Source
v10.0.303Compare Source
v10.0.302: .NET 10.0.10Compare Source
Release
What's Changed
PosixSignalRegistrationby @jonathanpeppers in #52466dotnet runby @jonathanpeppers in #52608dotnet run -e FOO=BARpasses@(RuntimeEnvironmentVariable)by @jonathanpeppers in #526642902832by @dotnet-bot in #53009$(Device)global property missing duringDeployToDevicetarget by @jonathanpeppers in #53018#:includeby @jjonescz in #523472912121by @dotnet-bot in #531232914767by @dotnet-bot in #53195dotnet tool exec- running dnx is implicit approval by @marcpopMSFT with @Copilot in #529562918587by @dotnet-bot in #532442918883by @dotnet-bot in #532702921244by @dotnet-bot in #53323--artifacts-pathsupport todotnet testin MTP mode by @Youssef1313 with @Copilot in #53353.csin file-based app virtual.csprojfile name by @jjonescz in #53182dotnet tool exec/dnxfailing when tool exists indotnet-tools.jsonbut not yet restored by @marcpopMSFT with @Copilot in #53361NETSDK1005when project refs different TFMs by @jonathanpeppers in #535232934590by @dotnet-bot in #53554Configuration
📅 Schedule: (in timezone America/Vancouver)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.