Downgrade detected, no downgrade performed

[unborn shoal]

I am running ErsatzTV version 25.9.0-docker-amd64, and it is complaining about a downgrade, but I have never downgraded. I remember this "MediaFilePath" issue being in a time period where I briefly had to run the development version, but I UPGRADED to the next release version shortly afterward when the issue was fixed in the release version.

[17:31:49 FTL] Downgrade detected! Database has migrations not known to this version of ErsatzTV: ["20250723030616_Update_MediaFilePath"]

I am running against MySQL and I do see a matching entry in the "__EFMigrationsHistory" table.

[granite carbon]

thanks for the additional context. you are right, this is a bug if you happened to install a couple specific releases earlier this year. i will fix tomorrow

[unborn shoal]

Thanks!

[granite carbon]

can you give the exact database version? mysql v something? mariadb something?

the migration you have listed there 20250723030616_Update_MediaFilePath was removed from etv, which explains why the health check thinks a downgrade happened (db says a migration happened, but etv doesn't have that migration anymore)

the reason it was removed was because it failed to apply successfully on mysql

so i'm not quite sure how you got it to work/how it ended up in your migration history table

[unborn shoal]

I am running a MariaDB 10.5.29 container on a separate server.

[granite carbon]

ok - important detail, thanks. mariadb is different than mysql

it looks like the migration that i deleted was successful against mariadb, which explains the downgrade warning

i can fix

[unborn shoal]

Yeah, MariaDB can be a little more forgiving. I think I've been running 10.5.x since I installed the instance.

[granite carbon]

ok, the health check should be fixed now on latest develop build #features-and-changes message