That faulty 8.5.3 upgrade package
Permalink
What is being done to remedey the faulty migrations in the V8.5.3 upgrade package, does anyone know?
For those unaware, apparently there's an issue with the migration IDs in the upgrade package meaning some migrations don't get run. This most obviously affects Express behaviour though you may not notice anything if you don't use Express.
Is the only solution to go back to V8.5.2 from a backup if you're lucky enough to have one or is a fix coming in e.g. 8.5.5 ?
I've got to roll a large commercial site back to the snapshot I took before I started upgrading and then upgrade it to 8.5.2 which is a real pain as over the last week they've had 200 more users which we can't just lose with a rollback.
For those unaware, apparently there's an issue with the migration IDs in the upgrade package meaning some migrations don't get run. This most obviously affects Express behaviour though you may not notice anything if you don't use Express.
Is the only solution to go back to V8.5.2 from a backup if you're lucky enough to have one or is a fix coming in e.g. 8.5.5 ?
I've got to roll a large commercial site back to the snapshot I took before I started upgrading and then upgrade it to 8.5.2 which is a real pain as over the last week they've had 200 more users which we can't just lose with a rollback.
