Closed CREITZ25 closed 1 year ago
@CREITZ25 thanks for your fast PR. However, you did not get what I was suggesting. We cannot easily undo the chaos created by the old migration script replacing every
u
withultimate
, etc. So here you added a new migration as a corrected "copy" of the 2023.07.001 migration.Instead of adding a new migration that will run after the old and broken one, we need to change the existing
2023.07.001
migration. This will not help for people who have already installed 2023.07.001 but it will help for all users that upgrade from <= 2023.04.001 starting from the day when we have released the fix. If we hurry up, we can ship a 2023.07.002 release with no other change than this fix until Thursday or Friday this week what would help a lot.
@hohwille Yes, your are right. Now we have the corrected file 2023.07.001. 2023.07.001-change - the same, but correct (I hope so) 2023.07.001-add - same script, but the EDITION is not changed, it is added 2023.07.001-repair - repairs error because of 2023.07.001
Fixes #1260 I just created and linked that issue that I also added to our CHANGELOG.