Select Page

Release analysis · November 12, 2026

Can you upgrade a MySQL application to EF Core 11 today? The answer depends on the exact provider package and its release status. A new .NET runtime does not make every database provider compatible with a new EF major. Check the package graph before rewriting application code.

Evidence checked November 12, 2026. This article covers Pomelo and Oracle’s MySQL provider. It does not establish compatibility for every commercial provider, and we have not executed a MySQL integration test for the combinations below.

What the release evidence currently shows

Microsoft.EntityFrameworkCore 11.0.0 is listed as a stable NuGet package targeting net11.0, listed with a November 10 update date. Some overview documentation still contains development-era wording; the released package does not establish third-party provider readiness.

The .NET 11 announcement states that EF Core 11 requires .NET 11. Microsoft’s provider guidance warns that providers generally do not work across EF major versions. Check vendor documentation and package dependencies rather than assuming matching framework badges imply matching EF support.

Verified package snapshot, November 12, 2026
Provider Observed release What this establishes
Pomelo.EntityFrameworkCore.MySql 9.0.0 stable Its GitHub release declares EF Core 9.0.x compatibility; this is not evidence of EF11 support.
MySql.EntityFrameworkCore 10.0.12 stable The current NuGet stable listing documents EF8, EF9 and EF10 support.
MySql.EntityFrameworkCore 11.0.0-preview A prerelease exists. Its net11.0 dependency group has an EF11 preview lower bound (11.0.0-preview.7.26381.103). That range admits final 11.0.0; dependency resolution is not vendor certification of final EF11 compatibility.

See Pomelo on NuGet, its GitHub release notes, Oracle’s stable package and preview package. Oracle’s compatibility table still describes EF11 preview/RC support for Connector/NET 26.10.0. Recheck these dated observations before choosing a production combination.

Separate three different upgrades

Track runtime targeting, EF Core and the provider as separate rows in your upgrade plan. Add the ADO.NET driver and server version as further rows. Pomelo uses MySqlConnector; Oracle’s provider uses its own Connector/NET stack. Substituting one provider for another changes more than a package name.

NuGet can show a package as usable by a later target framework while its EF dependencies remain tied to an earlier major. A successful restore answers dependency resolution questions. It does not demonstrate that provider-specific query translation, migrations or server features behave correctly. Keep the resolved package versions and dependency groups as evidence for each candidate.

If you want to move only the runtime, evaluate that specific combination against vendor support guidance and integration tests. Do not describe retaining an older EF stack as adopting EF11. The .NET support table shows .NET 8 and 9 reached end of support on November 10, 2026. Separately, the EF Core lifecycle table lists EF Core 9 support ending on that same date. Pomelo’s observed stable EF9 path therefore needs an explicit support assessment; moving the runtime alone does not extend EF9 servicing. Recheck the lifecycle tables and vendor guidance before deploying.

Build a small readiness matrix for your application

Use one row per candidate combination and record runtime, EF, provider, driver, server, maturity, vendor support statement and test result. Include an evidence URL and date. Keep “not verified” as an explicit state instead of treating an empty cell as a pass.

Start with the current production combination so the test harness proves it can connect, create its disposable schema and run meaningful assertions. Then change one dependency group at a time. Use a dedicated test database with representative server settings, collation, SQL modes and authentication. An in-memory substitute cannot validate MySQL translation.

Test the queries that define correctness

Prioritize decimal precision, date/time round trips, nullable values, case-sensitive comparisons, JSON queries, generated keys and concurrency handling. Test pagination with a deterministic sort, transactions with failures, cancellation, and connection reuse. Compare result values and row counts before considering speed.

EF11 changes query generation, so inspect its feature documentation when deciding what to exercise. A LINQ operator becoming available in EF does not establish translation support in every database provider. Build a focused reproduction for your own expensive queries and check the resulting SQL and execution plan.

Review migrations as a separate release artifact

Create a migration in a throwaway branch, inspect the generated operations and produce the deployment SQL for review. Unexpected column rewrites, collation changes or index rebuilds deserve investigation. Apply the migration to a restored disposable database with realistic data volume, then run both application and rollback checks.

Read EF11 breaking changes and the provider changelog. EF11 now throws by default when Migrate() or MigrateAsync() finds no migrations in the migrations assembly. The documented RelationalEventId.MigrationsNotFound warning configuration can suppress or log this condition; decide intentionally whether an empty migration set is valid for your application. Teams jumping several majors need the intervening compatibility notes as well.

Choose a release gate rather than a guessed date

For a stable-only production policy, wait for explicit vendor support for the final EF11 combination and successful application tests. A preview package can be useful in an isolated evaluation branch, with failures reported upstream using a minimal reproduction. Do not assign an arrival date that the maintainer has not committed to.

Changing providers can be worthwhile, but budget it as a migration with model, SQL and operational differences to validate. The immediate next step is a dated compatibility record and a working database test suite. Those make the eventual package release actionable instead of restarting the investigation each November.

Use the broader .NET 11 upgrade checklist for hardware, build environments and deployment rollback after resolving provider readiness.

Share This