.NET Standard 2.1 is now supported as a target framework for Entity Framework projects, enabling compatibility with Entity Framework 6. (Bug #117976, Bug #37837374)

GSSAPI/Kerberos authentication using the authentication_ldap_sasl_client plug-in is now supported on Windows. (WL #15984)

Connector/NET now supports the .NET 10 and Entity Framework Core 10 preview versions. (WL #16900)

Added to the test suite a new test for pure Kerberos authentication with Connector/NET. (Bug #38029691)

An invalid cast exception occurred with CreateMigrationDatabaseLock() when using the Entity Framework Core, which has been fixed by this patch.

Our thanks to Dev Nullinside for the contribution. (Bug #118282, Bug #38001821)

The number of usable connections may drop below the set MinPoolSize of the connection pool after a short period of time. This was because the latest connections were often picked for reuse, leaving the older connections to be idle and eventually dropped. This fix makes sure all connections in the pool have the opportunity to be reused, thus keeping a good pool size. (Bug #117020, Bug #37462116)

When using Entity Framework Core migrations to update the database schema with MySql.EntityFrameworkCore version 8.0.8, a System.NullReferenceException occured during the execution of a migration that included a RenameColumn operation. (Bug #116704, Bug #37462099)

Calling the MySqlHelper.ExecuteReaderAsync(string connectionString, string commandText, params MySqlParameter[] commandParameters) overload caused a stack overflow. (Bug #114006, Bug #36303124)

When using EFCore, schema name in the ToTable() method was always ignored, with entities always mapping to the schema specified in the database name in the connection string. With this fix, the schema name specified in ToTable() is now honored.

Our thanks to Stéphane Graziano for the contribution. (Bug #111030, Bug #35392218)

When an application used an asynchronous method and the cancellationToken was triggered, Connector/NET threw an exception from a different thread, which could not be caught and broke the execution. This fix corrected this behavior by throwing the exception in the main thread. (Bug #110789, Bug #35474099)