Feature Request: Safer native support for hotfix emergency releases in multi‑branch Git workflow

Describe the use case

In many enterprise projects, we maintain Git main branch plus hotfix branches for emergency bug fixes.

Typical workflow:

1. Main branch keeps iterating, production database has been migrated to version V10.
2. Critical bug found in production. We cut a hotfix branch from an older release tag.
3. We write a schema/data fix migration script for this hotfix. Logically this fix should apply before V10.

Current behaviour

1. Default outOfOrder=false: The lower‑version hotfix migration file is ignored, it will not be executed, and the bug remains unfixed.
2. If we turn on outOfOrder=true: The migration will run, but marked as Out of Order. Official documentation explicitly warns that re‑playing full migration history may yield different results, which brings consistency risk across dev/test/production environments. We cannot enable this as standard production practice.
3. cherryPick can force‑execute specified lower‑version migrations, but this feature is exclusive to Teams / Enterprise, not available in Community Edition.

Current official workaround for Community users: assign a higher version number (like V10.1__hotfix.sql), write fully idempotent SQL, and merge the hotfix migration back into main branch. This is purely manual discipline and easy for human error in large teams.

Expected behaviour

Hope Flyway Community Edition can provide a native, safe mechanism for emergency hotfix migrations:

• Avoid silently ignoring valid hotfix migrations
• Avoid the risks introduced by outOfOrder=true
• Do not require purchasing commercial license for basic hotfix capability

Possible directions for consideration:

1. A dedicated hotfix‑style migration file type that runs regardless of existing version sequence without polluting normal version history;
2. A safe community‑level subset of cherry‑pick functionality for emergency scenarios;
3. Other design that keeps the core principle: dev/test/prod migration history consistency.

Your environment

• Flyway: Community Edition (latest release v12/v13)
• Database: any
• Deployment: SpringBoot embedded + CI/CD GitOps multi‑branch workflow