Skip to content

Update dependency Microsoft.EntityFrameworkCore.SqlServer to v10#39

Closed
renovate[bot] wants to merge 2 commits into
mainfrom
renovate/major-dotnet-monorepo
Closed

Update dependency Microsoft.EntityFrameworkCore.SqlServer to v10#39
renovate[bot] wants to merge 2 commits into
mainfrom
renovate/major-dotnet-monorepo

Conversation

@renovate

@renovate renovate Bot commented Apr 17, 2026

Copy link
Copy Markdown

This PR contains the following updates:

Package Change Age Confidence
Microsoft.EntityFrameworkCore.SqlServer (source) [3.1.32][10.0.6] age confidence
Microsoft.EntityFrameworkCore.SqlServer (source) 8.0.2310.0.6 age confidence

Release Notes

dotnet/dotnet (Microsoft.EntityFrameworkCore.SqlServer)

v10.0.6

v10.0.5

v10.0.4

v10.0.3

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

v8.0.18: .NET 8.0.18

You can build .NET 8.0 from the repository by cloning the release tag v8.0.18 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.17: .NET 8.0.17

You can build .NET 8.0 from the repository by cloning the release tag v8.0.17 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.16: .NET 8.0.16

You can build .NET 8.0 from the repository by cloning the release tag v8.0.16 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.15: .NET 8.0.15

You can build .NET 8.0 from the repository by cloning the release tag v8.0.15 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.14: .NET 8.0.14

You can build .NET 8.0 from the repository by cloning the release tag v8.0.14 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.13: .NET 8.0.13

You can build .NET 8.0 from the repository by cloning the release tag v8.0.13 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.12: .NET 8.0.12

You can build .NET 8.0 from the repository by cloning the release tag v8.0.12 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.11: .NET 8.0.11

You can build .NET 8.0 from the repository by cloning the release tag v8.0.11 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.10: .NET 8.0.10

You can build .NET 8.0 from the repository by cloning the release tag v8.0.10 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.8: .NET 8.0.8

You can build .NET 8.0 from the repository by cloning the release tag v8.0.8 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.7: .NET 8.0.7

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

v8.0.6: .NET 8.0.6

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

v8.0.5: .NET 8.0.5

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

v8.0.4: .NET 8.0.4

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

v8.0.3: .NET 8.0.3

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

v8.0.2: .NET 8.0.2

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

v8.0.1: .NET 8.0.1

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

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


Configuration

📅 Schedule: (UTC)

  • 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
Copy Markdown

🚀 AI Library Upgrade workflow started

Checkout and dependency detection in progress. You will see further updates as each step completes.

@CodeLogicAI

Copy link
Copy Markdown

AI Library Upgrade - Comparison Job Timeout

The comparison job (ID: 7b525784-782d-4566-9748-c01f3005cadb) exceeded the configured timeout of 1440 minutes (elapsed: 1440 minutes).

Proceeding with fallback implementation based on the PR diff.

💡 Configure your CI to post build results back to CodeLogic via the Build Pipeline Data API.

Documentation: https://docs.codelogic.com/Send_Build_Info/

@CodeLogicAI

Copy link
Copy Markdown

🚀 Starting AI implementation...

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

Workflow Status

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

Updated EF Core versions to be compatible with each target framework:
- net462: Use EF Core 3.1.32 (last version supporting .NET Framework)
- net8.0: Use EF Core 8.0.23 (maximum version compatible with .NET 8)
- net10.0: Use EF Core 10.0.6 (as specified in upgrade)
- Directory.Packages.props: Updated to EF Core 10.0.6

This fixes build errors where EF Core 10.0.6 was specified for net462
and net8.0 targets, which don't support this version. EF Core 10.x
only supports .NET 10 and later.

The build now succeeds for all target frameworks.
@CodeLogicAI

Copy link
Copy Markdown

✅ AI Library Upgrade Workflow Complete

Workflow Status

Step Status
DETECT_DEPENDENCIES ✅ SUCCESS
SPECIALIZED_SCAN ⏭️ SKIPPED
DIFF_COMPLETE ✅ SUCCESS
TICKET_GENERATION ⏭️ SKIPPED
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: 7b525784-782d-4566-9748-c01f3005cadb
  • Diff MVD: a7f741c0-8875-4d46-950f-32efc5e740b0
  • Status: Commits pushed successfully

Please review the changes and ensure they meet your requirements.


Generated by CodeLogic AI Library Upgrade

@renovate

renovate Bot commented Apr 18, 2026

Copy link
Copy Markdown
Author

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 closed this May 27, 2026
@renovate

renovate Bot commented May 27, 2026

Copy link
Copy Markdown
Author

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 10.x releases. But if you manually upgrade to 10.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate Bot deleted the renovate/major-dotnet-monorepo branch May 27, 2026 14:45
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