title: How to force FluentMigrator to run migration even if DB version matches
body: <p>I use FluentMigrator 3.2.1 &amp; dotnet-fm too to run migrations.
  Imagine that I have database versions 1,2,3,4 and so on, classes are marked with</p>
  
  <pre><code>[FluentMigrator.Migration(1, "1")]
   [FluentMigrator.Migration(2, "2")]
   [FluentMigrator.Migration(3, "3")]
   [FluentMigrator.Migration(4, "4")]
  </code></pre>
  
  <p>and all of them have overriden Up() and Down() methods.
  While in dev env, I have DB version 4. I modify "up" script with a new version of a stored procedure. Database already has version 4 in VersionInfo table, and I execute this command</p>
  
  <pre><code>dotnet-fm migrate -p Postgres -c "Server=192.168...server info" -a "/mnt/d/src/........DB.dll" up
  </code></pre>
  
  <p>I would like the migrator to do "force" update to the version 4 again, but looks like is sees that version of the DB is already 4.
  I use to rollback to 3 and the roll forward to the latest, but it is not convenient and is not suitable for CI/CD.
  Is there any elegant way to "force" the "up" migration, f.ex. with migration tags?</p>