Upgrading from 2.x to 3.x on main branch currently broken

[aurorasmiles]

Since the postgres/greenlight migrations are currently only in the develop-branch, running ./scripts/upgrade on an existing installation currently breaks the installation

[lightweight]

Hmm. I'm not sure if something's been fixed in the last couple days (but doesn't look like there've been any new commits?)... but I just did an upgrade from 2.7.x->3.x (before I saw your post here - saw it while the upgrade was proceeding - gulp!), but the upgrade went fine, and the Greenlight upgrade was fine, too (to 3.5.0), even upgrading my instance (automatically, via the upgrade script) from PostgreSQL 12 -> 16... Could it be that I was just lucky?

[aurorasmiles]

Even after manually pulling in https://github.com/bigbluebutton/docker/blob/develop/scripts/upgrade and https://github.com/bigbluebutton/docker/blob/develop/scripts/postgres-migrate from the develop-branch we ran into some issues, before that the postgress/greenlight data was still in the respective -data folder, and not in data/, but even after that it seemed like our data wasn't properly loaded, so we ended up loading in a backup for 2.x