DB Migrations might not be running

[Laikar]

I run seafile deployed using the docker containers provided by ggogel, so i don't exactly know where the issue originates from, i already opened an issue there ggogel/seafile-containerized#292.

I activated
CLIENT_SSO_VIA_LOCAL_BROWSER = True
To login with system browser in seafile clients, but when enabled, clients fail to get sso url, and on server logs the following message appears

seahub-1 | 2024-08-13 14:21:26,656 [ERROR] seahub.api2.endpoints.sso.client_sso_link:54 post (1146, "Table 'seahub_db.base_clientssotoken' doesn't exist")
seahub-1 | 2024-08-13 14:21:26,657 [ERROR] django.request:241 log_response Internal Server Error: /api2/client-sso-link/

Looking through the Seafile sources, that table is created in the v11.0.0 db migrations script or what i guess is the initial DB setup.
The original problem was fixed by manually crating the DB using the v11.0.0 migration script linked above.

I've been running this deployment since version 9, so my only guess is that migrations aren't running for whatever reason, I will backup the DB and try to run migrations on a separate testing environment and report what I find.