Mysql deployment script generated in EF Core 5.0 doesn't support DDL transaction rollback

Question

We are using EF core 5.0 with pomelo mysql db provider. We generate an idempotent sql script to add migration using efcore migration commands. We noticed that the transactions are not rolled back if there are db connection or timeout errors.

How can we ensure the generated script is idempotent, since in the existing state it doesn't behave right.