Ok what will be our issue tracking policy for old “migration code”? Open a separate issue or work on the same Pull Request?
In other packages I just removed the “migration code” (DB keys, migration fragments) and pushed directly on v7. So think we can analyze the single case here, then add a commit to a Pull Request that will be merged on v7.