Error messages of failed operations include the reason of an unexpected exception (for example
Can not execute non-query SQL: <reason>), and MigrationResult.Exception holds the exception itself.
Migrations running in a transaction (the default) failed with "Can not execute non-query SQL": commands were not
attached to the transaction, which SqlClient requires. Script migrations, code migrations using the migration
connection and the journal record now run in the migration transaction.
Breaking: dropped net8.0 and the netstandard2.0, netstandard2.1, netcoreapp3.1, net6.0 and net7.0 targets. Supported targets are net9.0 and net10.0: stay on 5.x for older runtimes.
Breaking:Microsoft.Data.SqlClient 7.0.0 (was 6.1.4): a new major version, see its release notes if your application references SqlClient directly.
Breaking: package renamed from Curiosity.Migrations.SqlServer to Curiosus.Migrations.SqlServer and now published by the curiosus-dev organization. Namespaces, assemblies and types were renamed accordingly (Curiosity* → Curiosus*): replace Curiosity with Curiosus in your code to migrate.