migration x was previously applied but has been modified skip

[jonatansalemes]

I have found these related issues/pull requests

i have no found related issues

Description

I have some use cases which i have applied some migrations in production db, after some linters were introduced I cant go further since I added a new line at the end of the previous file to be compliance with new linter.

Can we improve migrate run command to accept like --no-checksum and just logging as warn that file was skipped but modified and continue applying new files ? or new option like migrate --fix-checksum to catch new checksums based on new content and update _sqlx_migrations table

Some(applied_migration) => {
                if migration.checksum != applied_migration.checksum {
                    bail!(MigrateError::VersionMismatch(migration.version));
                }
            }

Prefered solution

creation of new options on slqx migrate run like --no-checksum or --fix-checksum

Is this a breaking change? Why or why not?

no. default options behaviour as the same. use must explicit use new options