Skip to content
Snippets Groups Projects
This project is mirrored from https://github.com/metabase/metabase. Pull mirroring updated .
  1. May 23, 2024
  2. May 21, 2024
    • John Swanson's avatar
      Fix `report_card.collection_preview` in v49 (#42921) · bab351f5
      John Swanson authored
      This is a bit painful. I merged this change, but realized we need to
      backport the fix to v49. However:
      
      - we don't want to have two versions of the migration (one with a v49
      id, one with a v50 id) because then if someone upgrades to 50, then
      downgrades to 49, the `rollback` will run and change the type back,
      leading to a bug.
      
      - we don't want to push a v51 changeSet ID to v49 or v50, because we
      give the user a helpful notice when their database needs a downgrade.
      We do this by checking for the latest *executed* migration in the
      database and comparing it to the latest migration that Liquibase knows
      about, and making sure the executed isn't bigger than the known (e.g.
      you can't have executed a v51 migration if it isn't in the local
      migration yaml). That would all work fine, except that then we want to
      tell you how to downgrade your database, and we use the latest-executed
      version for that. So if, for example, someone upgraded from 48 to 49 and
      got a v51 changeset, then downgraded back to 48, they would get an error
      telling them to run the *v51* jar to roll back their DB.
      
      In this case though, I think it's fine to just move the migration around
      to v49, then we can backport it to 49 and 50.
  3. May 20, 2024
  4. May 17, 2024
  5. May 16, 2024
  6. May 15, 2024
  7. May 14, 2024
  8. May 13, 2024
  9. May 10, 2024
  10. May 09, 2024
Loading