mirror of
https://github.com/TryGhost/Ghost.git
synced 2025-02-10 23:36:14 -05:00
b788604e15
refs https://github.com/TryGhost/Toolbox/issues/300 - the previous commit deleted all v1/v2/v3 migrations - Ghost-CLI forces you to update to the latest minor in your major before you upgrade but people who aren't on the latest minor, who don't use Ghost-CLI and try to update to v5 might have missed migrations that I've just deleted - the way to protect against this is to add some migrations for the last minor in each major, that will throw an error if they get run - this uses a feature of knex-migrator where it will always try to backfill missing migrations when you run Ghost, so these new migrations should _only_ be run if the Ghost DB hasn't already run the same number of migrations in that minor - by throwing an error, it'll cause knex-migrator to fail and the user shouldn't be able to update, which is good - v2 and v3 only have 1 migration so I can just replace that, but v1 has 2 migrations. I think it makes more sense that the first one errors and the second one is a no-op otherwise it'll run the first migration, succeed, run the second, error, and then rollback the second and first one - the new migration names are different from the original ones but that shouldn't matter because we're not comparing nor storing them |
||
|---|---|---|
| .. | ||
| 1.25 | ||
| 2.37 | ||
| 3.41 | ||
| 4.0 | ||
| 4.1 | ||
| 4.2 | ||
| 4.3 | ||
| 4.4 | ||
| 4.5 | ||
| 4.6 | ||
| 4.7 | ||
| 4.8 | ||
| 4.9 | ||
| 4.11 | ||
| 4.12 | ||
| 4.13 | ||
| 4.14 | ||
| 4.15 | ||
| 4.16 | ||
| 4.17 | ||
| 4.19 | ||
| 4.20 | ||
| 4.22 | ||
| 4.23 | ||
| 4.33 | ||
| 4.34 | ||
| 4.35 | ||
| 4.36 | ||
| 4.37 | ||
| 4.38 | ||
| 4.39 | ||
| 4.40 | ||
| 4.42 | ||
| 4.43 | ||
| 4.44 | ||
| 4.45 | ||
| 4.46 | ||