Skip to content

Conversation

@renovate-bot
Copy link
Contributor

@renovate-bot renovate-bot commented Nov 12, 2025

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

This PR contains the following updates:

Package Change Age Confidence Type Update
Microsoft.AspNetCore.TestHost (source) 8.0.22 -> 10.0.0 age confidence nuget major
dotnet-sdk 8.0.416 -> 10.0.100 age confidence dotnet-sdk major

Release Notes

dotnet/dotnet (Microsoft.AspNetCore.TestHost)

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

dotnet/sdk (dotnet-sdk)

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: .NET 9.0.10

Compare Source

Release

What's Changed

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

v9.0.305: .NET 9.0.9

Compare Source

Release

What's Changed


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.

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

@jskeet jskeet added the do not merge PRs with this label should not be merged label Nov 12, 2025
@jskeet
Copy link
Member

jskeet commented Nov 12, 2025

Closing this PR will just recreate it. Marked as "do not merge" instead.

@renovate-bot renovate-bot force-pushed the renovate/major-dotnet-monorepo branch from 6faa24f to c48cdf0 Compare November 12, 2025 15:53
@renovate-bot renovate-bot changed the title chore(deps): update dotnet monorepo (major) chore(deps): update dotnet monorepo to v10 (major) Nov 12, 2025
@renovate-bot renovate-bot force-pushed the renovate/major-dotnet-monorepo branch from c48cdf0 to 8077d21 Compare November 17, 2025 18:50
@renovate-bot renovate-bot force-pushed the renovate/major-dotnet-monorepo branch from 8077d21 to 6e7b349 Compare November 18, 2025 23:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do not merge PRs with this label should not be merged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants