Update dotnet monorepo

[thomhurst]

This PR contains the following updates:

Package	Change	Age	Confidence
FSharp.Core (source)	10.1.302 → 10.1.400
Microsoft.AspNetCore.SignalR.Client (source)	10.0.10 → 10.0.11
Microsoft.Extensions.Caching.Memory (source)	10.0.10 → 10.0.11
Microsoft.Extensions.DependencyInjection (source)	10.0.10 → 10.0.11
Microsoft.Extensions.Hosting (source)	10.0.10 → 10.0.11
Microsoft.Extensions.Http (source)	10.0.10 → 10.0.11
Microsoft.SourceLink.GitHub	10.0.301 → 10.0.400
System.CommandLine (source)	2.0.10 → 2.0.11
microsoft.dotnet.apicompat.tool (source)	10.0.302 → 10.0.400

---

Release Notes

dotnet/dotnet (Microsoft.SourceLink.GitHub)

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

---

Configuration

📅 Schedule: (UTC)

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

🚦 Automerge: Enabled.

♻ 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.

---

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

---

This PR has been generated by Mend Renovate CLI.

[coderabbitai]

Warning

Review limit reached

@thomhurst, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 14 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: fad7a1ae-5d60-4702-bce8-6cf4db33903e

📥 Commits

Reviewing files that changed from the base of the PR and between 991605c and 81cb4e8.

📒 Files selected for processing (2)

• .config/dotnet-tools.json
• Directory.Packages.props

---

_{Comment @coderabbitai help to get the list of available commands.}

[claude]

Code review

No issues found. This is an automated Renovate dependency-bump PR touching only .config/dotnet-tools.json and Directory.Packages.props — three patch-level version bumps (Microsoft.SourceLink.GitHub 10.0.301→10.0.303, System.CommandLine 2.0.10→2.0.11, microsoft.dotnet.apicompat.tool 10.0.302→10.0.303). No source code changes are included, and the version bumps match the PR description consistently across both files. Nothing to flag for correctness or architecture.

[claude]

Code Review

This is an automated dependency-bump PR (Renovate: "Update dotnet monorepo") touching only two manifest files:

• .config/dotnet-tools.json — bumps microsoft.dotnet.apicompat.tool from 10.0.302 → 10.0.400.
• Directory.Packages.props — bumps FSharp.Core, several Microsoft.Extensions.* packages, Microsoft.SourceLink.GitHub, Microsoft.AspNetCore.SignalR.Client, and System.CommandLine to newer patch/minor versions.

There is no source code, logic, or behavior change in this diff — it's purely version-number edits in dependency manifests, so there's no design pattern, abstraction, or architectural concern to evaluate here.

LGTM — no issues found. Recommend relying on CI (build, tests, API-compat check given the apicompat tool bump) to confirm the new package versions don't introduce breaking changes before merge.