Metabae v0.50.0 was rolled back

I installed the new Update v0.50 this morning, now I can't find it on dockerhub and I can't rollback my database to v0.49.13

I get this error You must run java -jar metabase.jar migrate down from version 50.

metabase/metabase:latest on dockerhub is on v0.49.15 so you rolled back the v0.50.0

what i should do now, I'll lose everything like this?

how to roll back to v0.49.13

Are you on v50 now? Why do you want to roll back?

BTW: we found an error that we’re fixing today l, that’s why we took the version out of the page, but no big deal

1 Like

@Luiggi
I can't install v0.50.0 again thats why i want to roll back.

how to roll back or how to install the v0.50.0 again?

Which version are you in right now?

@Luiggi
my metabasedb on v0.50.0

so i want to rollback or install v0.50.0

Is Metabase working right now?

@Luiggi
no i delete the image.

@Luiggi

Any feedback? please i need help here

Are you using docker? What happens when you do docker pull metabase/metabase:v0.49.15?

@vamsi

I get this error

clojure.lang.ExceptionInfo: ERROR: Downgrade detected.

Your metabase instance appears to have been downgraded without a corresponding database downgrade.

You must run `java -jar metabase.jar migrate down` from version 50.

If you are not using MySQL as Metabase Database, you can simply use the metabase/metabase:v0.50.0-RC2 image to rollback. But if you are using MYSQL, then I suggest reading the diffs between v0.50.0-RC2 and v0.50.0 before rolling back.

1 Like

great answer

@Luiggi @Maiquu

I'm using postgres and I did use RC2 tag and still gave me the same error

clojure.lang.ExceptionInfo: ERROR: Downgrade detected.

Your metabase instance appears to have been downgraded without a corresponding database downgrade.

You must run `java -jar metabase.jar migrate down` from version 50.

@Luiggi

I installed v0.50.1 now and i can't see Model caching setting in the database or the cron schedule for it.

Did you remove it from the opensource version?

Not intentionally - this will be correct in v50.2:

v50.2 is now available, please upgrade to that version everyone