[BUG] CLI migration + Flow Trigger/Action releases

[Brian_S]

Hi!

We hit a major blocker migrating Flow legacy extensions using our CI/CD integration with Shopify CLI. It seems like there's possibly a couple large pitfalls in the latest CLI extension release flow.

Here's the steps that lead us to our current issue:

• We imported all the legacy extensions with shopify app import-flow-legacy-extensions , executed shopify app release locally to do the proper mapping the CLI asks to do.
• We released that version and committed the .env file that the CLI creates with the mapping so that in the next iteration the CI/CD process would pick up that mapping.
• Because of a manual error we created a version with NO extensions (just empty) but we did NOT release that version (we execute commands with --no-release) but somehow that broke the app's Flow actions and triggers. All of our customers using those actions/triggers had broken flows and saw the following UI:
• We temporarily solved that problem by releasing an older version via the extension release UI in our Shopify Partners dashboard

Now we want to create a new version and despite having the .env file, and despite not having ever released the empty version, and despite having the extensions work properly in the current released version.. the CLI prompts us to create new extensions and to remove the current ones. That would leave our merchants with broken flows again.

So a couple important questions: 

1. Why would that empty version break all of our merchants' flows even though we never released it? It seems way too easy to make a mistake like that.
2. [MOST IMPORTANTLY] Is there a way to remove the versions that have not been released and that seem to be messing with the CLI when doing this mapping again? We want to continue editing the currently live Flow triggers/actions without leading to merchants with broken Flows. 

Thanks in advance for your help!