Skip to content

Update dotnet monorepo to v10 (major)#13

Merged
garrmark merged 2 commits intomainfrom
renovate/major-dotnet-monorepo
Jan 26, 2026
Merged

Update dotnet monorepo to v10 (major)#13
garrmark merged 2 commits intomainfrom
renovate/major-dotnet-monorepo

Conversation

@renovate
Copy link

@renovate renovate bot commented Jan 26, 2026

ℹ️ 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) 9.0.110.0.2 age confidence nuget major
Microsoft.Data.Sqlite (source) 9.0.110.0.2 age confidence nuget major
Microsoft.EntityFrameworkCore.SqlServer (source) [3.1.10][10.0.2] age confidence nuget major
Microsoft.EntityFrameworkCore.SqlServer (source) 9.0.110.0.2 age confidence nuget major
Microsoft.SourceLink.GitHub 8.0.010.0.102 age confidence nuget major
System.Reflection.Metadata (source) 9.0.110.0.2 age confidence nuget major
dotnet-sdk 9.0.10110.0.102 age confidence dotnet-sdk major

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

dotnet/sdk (dotnet-sdk)

v10.0.102: .NET 10.0.2

Compare Source

Release

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

Compare Source

v9.0.309: .NET 9.0.12

Compare Source

Release

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


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.EntityFrameworkCore.SqlServer 9.0.1 10.0.2
NUGET_CSPROJ N/A Microsoft.Bcl.AsyncInterfaces 9.0.1 10.0.2
NUGET_CSPROJ N/A Microsoft.SourceLink.GitHub 8.0.0 10.0.102
NUGET_CSPROJ N/A System.Reflection.Metadata 9.0.1 10.0.2
NUGET_CSPROJ N/A Microsoft.Data.Sqlite 9.0.1 10.0.2

🔬 Scan Execution Details

  • Application: dapper-app
  • Scan space: https://github.com/CodeLogicIncEngineering/Dapper|renovate/major-dotnet-monorepo
  • Source scan id: scan-dotnet-sourcelibs-1769442871649

@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

@CodeLogicAI
Copy link

🚀 Starting AI implementation...

Beginning implementation of library upgrade changes. This may take several minutes.

Workflow Status

Step Status
DETECT_DEPENDENCIES ✅ SUCCESS
SPECIALIZED_SCAN ✅ SUCCESS
DIFF_COMPLETE ✅ SUCCESS
TICKET_GENERATION ✅ SUCCESS
TICKET_IMPLEMENTATION ⏳ PENDING
PUSH_CHANGES ⏳ PENDING

@CodeLogicAI
Copy link

AI-Generated Work Ticket Suggestions for Library Upgrades (Comparison Completed)


Analysis for Comparison Job: f634fa53-af4c-48dd-9e65-dcbea8a68e53 (Diff MVD: 9e5f5a70-c90a-4ee1-82f7-a6e4b0698dbb

Analysis completed. No definitive migration tickets were produced.

Proceeding to attempt AI implementation based on the PR diff using the fallback path.

💡 Configure your CI to post build results back to CodeLogic via the Build Pipeline Data API.\n\nDocumentation: https://docs.codelogic.com/Send_Build_Info/

This commit updates the Dapper solution to support .NET 10:
- Updated NuGet package versions to .NET 10 compatible versions
- Added net10.0 target framework to main library, tests, and benchmarks
- Updated Microsoft.Data.SqlClient from 6.0.1 to 6.1.1 (required by EF Core 10)
- Updated Azure.Identity from 1.13.2 to 1.14.2 (required by Microsoft.Data.SqlClient 6.1.1)
- Fixed EF Core version compatibility for different target frameworks:
  - net462: EF Core 3.1.10 (last version supporting .NET Framework)
  - net8.0: EF Core 9.0.1
  - net10.0: EF Core 10.0.2

All projects now build successfully with .NET SDK 10.0.102.
@CodeLogicAI
Copy link

✅ AI Library Upgrade Workflow Complete

Workflow Status

Step Status
DETECT_DEPENDENCIES ✅ SUCCESS
SPECIALIZED_SCAN ✅ SUCCESS
DIFF_COMPLETE ✅ SUCCESS
TICKET_GENERATION ✅ SUCCESS
TICKET_IMPLEMENTATION ✅ SUCCESS
PUSH_CHANGES ✅ SUCCESS

Result: Changes Successfully Implemented

✅ The AI has successfully implemented the library upgrade changes and pushed them to this PR.

Summary:

  • Comparison Job: f634fa53-af4c-48dd-9e65-dcbea8a68e53
  • Diff MVD: 9e5f5a70-c90a-4ee1-82f7-a6e4b0698dbb
  • Status: Commits pushed successfully

Please review the changes and ensure they meet your requirements.


Generated by CodeLogic AI Library Upgrade

@renovate
Copy link
Author

renovate bot commented Jan 26, 2026

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@garrmark garrmark merged commit 7e55a06 into main Jan 26, 2026
1 check passed
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