Skip to content

Update dotnet monorepo (major)#757

Closed
renovate[bot] wants to merge 1 commit intodevelopfrom
renovate/major-dotnet-monorepo
Closed

Update dotnet monorepo (major)#757
renovate[bot] wants to merge 1 commit intodevelopfrom
renovate/major-dotnet-monorepo

Conversation

@renovate
Copy link

@renovate renovate bot commented Feb 6, 2026

This PR contains the following updates:

Package Change Age Confidence
Microsoft.Bcl.AsyncInterfaces (source) 8.0.010.0.2 age confidence
Microsoft.CodeAnalysis.CSharp 4.14.05.0.0 age confidence
Microsoft.Extensions.DependencyInjection (source) 8.0.110.0.2 age confidence
Microsoft.SourceLink.GitHub 8.0.010.0.102 age confidence

Release Notes

dotnet/dotnet (Microsoft.Bcl.AsyncInterfaces)

v10.0.2

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


Configuration

📅 Schedule: 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.

@CodeLogicAI
Copy link

🚀 Library Upgrade Analysis Initiated

Relevant library changes detected. Specialized scans are being initiated.

📋 Direct Dependency Changes

Type Group ID Artifact ID Old Version New Version
NUGET_CSPROJ N/A Microsoft.SourceLink.GitHub 8.0.0 10.0.102
NUGET_CSPROJ N/A Microsoft.Bcl.AsyncInterfaces 8.0.0 10.0.2
NUGET_CSPROJ N/A Microsoft.Extensions.DependencyInjection 8.0.1 10.0.2
NUGET_CSPROJ N/A Microsoft.CodeAnalysis.CSharp 4.14.0 5.0.0

🔬 Scan Execution Details

  • Application: dnn-app
  • Scan space: https://github.com/CodeLogicIncEngineering/Dnn.Platform|renovate/major-dotnet-monorepo|LibraryUpgradeScanSpace
  • Source scan id: scan-dotnet-sourcelibs-1770407773005

@CodeLogicAI
Copy link

Specialized Scans Completed

The specialized library scans have completed successfully. The next step is the comparison process and ticket creation.

The system will now:

  1. Compare the scan results to identify library upgrade impacts
  2. Generate work tickets with detailed migration recommendations

@garrmark garrmark closed this Feb 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants