Skip to content

chore(deps): update dotnet monorepo (major) #926

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
renovate-bot wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): update dotnet monorepo (major) #926

renovate-bot wants to merge 1 commit into from

Conversation

@renovate-bot
Copy link
Contributor

@renovate-bot renovate-bot commented Nov 12, 2025 •
edited
Loading

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Type Update
Microsoft.Bcl.AsyncInterfaces (source) 6.0.0 → 10.0.1 age confidence nuget major
Microsoft.CodeAnalysis.CSharp 4.14.0 → 5.0.0 age confidence nuget major
Microsoft.Extensions.Logging.Abstractions (source) 9.0.11 → 10.0.1 age confidence nuget major
System.Collections.Immutable (source) 9.0.11 → 10.0.1 age confidence nuget major
dotnet-sdk 8.0.416 → 10.0.101 age confidence dotnet-sdk major

Release Notes

dotnet/dotnet (Microsoft.Bcl.AsyncInterfaces)

v10.0.1

v9.0.7: .NET 9.0.7

You can build .NET 9.0 from the repository by cloning the release tag v9.0.7 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

v9.0.6: .NET 9.0.6

You can build .NET 9.0 from the repository by cloning the release tag v9.0.6 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

v9.0.5: .NET 9.0.5

You can build .NET 9.0 from the repository by cloning the release tag v9.0.5 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

v9.0.4: .NET 9.0.4

You can build .NET 9.0 from the repository by cloning the release tag v9.0.4 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

v9.0.3: .NET 9.0.3

You can build .NET 9.0 from the repository by cloning the release tag v9.0.3 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

v9.0.2: .NET 9.0.2

You can build .NET 9.0 from the repository by cloning the release tag v9.0.2 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

v9.0.1: .NET 9.0.1

You can build .NET 9.0 from the repository by cloning the release tag v9.0.1 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

v9.0.0: .NET 9.0.0

You can build .NET 9.0 from the repository by cloning the release tag v9.0.0 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

v8.0.0: .NET 8.0

You can build .NET 8.0 from the repository by cloning the release tag v8.0.0 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://dotnet.microsoft.com/download/dotnet/release-key-2023.asc

dotnet/sdk (dotnet-sdk)

v10.0.101: .NET 10.0.1

Compare Source

Release

What's Changed

Full Changelog: dotnet/sdk@v10.0.100...v10.0.101

v10.0.100: .NET 10.0.0

Compare Source

Release

What's Changed

Full Changelog: dotnet/sdk@v10.0.100-rc.2.25502.107...v10.0.100

v9.0.308

Compare Source

v9.0.307: .NET 9.0.11

Compare Source

Release

What's Changed

Full Changelog: dotnet/sdk@v9.0.306...v9.0.307

[v9.0.306](https://redirect.github.com/dotnet/sdk/releases/t

Configuration

📅 Schedule: Branch creation - "before 8am" in timezone Europe/London, 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.

👻 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 was generated by Mend Renovate. View the repository job log.

@renovate-bot renovate-bot requested a review from a team as a code owner November 12, 2025 07:39
@trusted-contributions-gcf trusted-contributions-gcf bot added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Nov 12, 2025
@gemini-code-assist
Copy link

gemini-code-assist bot commented Nov 12, 2025

Summary of Changes

Hello @renovate-bot, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request performs a significant upgrade of the project's .NET dependencies, moving from .NET 8 to .NET 9. This includes updating the core .NET SDK and several key Microsoft libraries to their latest major versions. The update aims to leverage the newest features, performance enhancements, and security improvements offered by the .NET 9 ecosystem, ensuring the project remains modern and well-supported.

Highlights

  • .NET SDK Upgrade: The project's .NET SDK has been upgraded from version "8.0.415" to "9.0.306", aligning with the latest .NET 9 development cycle.
  • Core Library Major Updates: Several foundational Microsoft libraries, including "Microsoft.Bcl.AsyncInterfaces", "Microsoft.Extensions.Logging.Abstractions", and "System.Collections.Immutable", have been updated to their major version "10.0.0".
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

gemini-code-assist[bot]
gemini-code-assist bot reviewed Nov 12, 2025
View reviewed changes
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request proposes a major update of the .NET dependencies, moving to the .NET 9 Preview SDK and several core packages to version 10.0.0. These package versions appear to be from a non-public, pre-release feed for a future version of .NET. This introduces significant risks of instability and breaking changes, especially with the large version jump for Microsoft.Bcl.AsyncInterfaces from v6 to v10. I have left comments highlighting the risks of using a preview SDK and highly experimental package versions. I recommend carefully evaluating the need for such an early adoption and considering using official .NET 9 preview packages as an alternative if aligning with the new SDK is the goal.

Directory.Packages.props Outdated
Comment on lines 23 to 26
<PackageVersion Include="Microsoft.Bcl.AsyncInterfaces" Version="10.0.0" />
<PackageVersion Include="Microsoft.CodeAnalysis.CSharp" Version="4.14.0" />
<PackageVersion Include="Microsoft.Extensions.Logging.Abstractions" Version="9.0.11" />
<PackageVersion Include="System.Collections.Immutable" Version="9.0.11" />
<PackageVersion Include="Microsoft.Extensions.Logging.Abstractions" Version="10.0.0" />
<PackageVersion Include="System.Collections.Immutable" Version="10.0.0" />
Copy link

@gemini-code-assist gemini-code-assist bot Nov 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

critical

This updates several core .NET packages to version 10.0.0. This version appears to be from a pre-release feed for a future, unannounced version of .NET, as public releases are currently on version 8 (stable) and 9 (preview).

Using such early, non-public versions is highly risky and can lead to:

  • Breaking Changes: Major version jumps, especially from v6 to v10 for Microsoft.Bcl.AsyncInterfaces, are very likely to contain significant breaking API changes.
  • Instability: These builds are not guaranteed to be stable.
  • Lack of Support: You will not find community support or official documentation for issues encountered with these versions.

It is strongly recommended to use official stable or preview releases from NuGet.org. If the goal is to align with the .NET 9 SDK, consider using the latest .NET 9 preview packages instead of these .NET 10 packages.

global.json Outdated
{
"sdk": {
"version": "8.0.415",
"version": "9.0.306",
Copy link

@gemini-code-assist gemini-code-assist bot Nov 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

Updating the .NET SDK to version 9.0.306 moves the project to a .NET 9 Preview SDK. While this might be intentional for testing upcoming features, it's important to be aware that preview SDKs can be unstable and are not recommended for production environments. This could introduce unexpected build issues or runtime behavior. Please ensure that this change is intentional and that the team is prepared to handle potential instability from using a preview SDK.

@jskeet
Copy link
Collaborator

jskeet commented Nov 12, 2025

@amanda-tarafa Another one I think we want to ignore - although we probably could take them other than global.json. Maybe figure out when to update to the .NET 10 SDK and do everything at that point?

@renovate-bot renovate-bot force-pushed the renovate/major-dotnet-monorepo branch from 9069aba to 40d6fba Compare November 12, 2025 12:45
@renovate-bot renovate-bot changed the title chore(deps): update dotnet monorepo (major) chore(deps): update dotnet monorepo to v10 (major) Nov 12, 2025
@amanda-tarafa amanda-tarafa self-assigned this Nov 13, 2025
@amanda-tarafa amanda-tarafa added the do not merge Indicates a pull request not ready for merge, due to either quality or timing. label Nov 13, 2025
@amanda-tarafa
Copy link
Contributor

amanda-tarafa commented Nov 13, 2025

Let's keep it around for now.

@renovate-bot renovate-bot force-pushed the renovate/major-dotnet-monorepo branch 3 times, most recently from 7e0cba5 to b07de28 Compare November 18, 2025 22:29
@renovate-bot renovate-bot changed the title chore(deps): update dotnet monorepo to v10 (major) chore(deps): update dotnet monorepo (major) Nov 18, 2025
@renovate-bot renovate-bot force-pushed the renovate/major-dotnet-monorepo branch 2 times, most recently from 5a44fb6 to 36f0aab Compare December 10, 2025 07:38
@renovate-bot renovate-bot force-pushed the renovate/major-dotnet-monorepo branch from 36f0aab to 6361c36 Compare December 10, 2025 12:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

1 more reviewer

@gemini-code-assist gemini-code-assist[bot] gemini-code-assist[bot] left review comments

Reviewers whose approvals may not affect merge requirements

At least 1 approving review is required to merge this pull request.

Assignees

@amanda-tarafa amanda-tarafa

Labels

do not merge Indicates a pull request not ready for merge, due to either quality or timing. kokoro:force-run Add this label to force Kokoro to re-run the tests.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@renovate-bot @jskeet @amanda-tarafa