You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
fix(bootstrap): refuse a 0.1.0 platform still on Gitea instead of starting Forgejo on its data #134
A platform installed with urbex 0.1.0 runs Gitea 1.24. Since #116 the forge role deploys Forgejo 15, and urbex bootstrap with a build of today's main starts it on Gitea's data volume. Forgejo refuses the database and exits:
Migration Error: Your database (migration version: 321) is for a newer Forgejo, you can not use the newer database for this old Forgejo release (305).
Forgejo will exit to keep your database safe and unchanged.
The data is untouched, but the forge stays down: builds and webhooks stop. I reproduced it locally with gitea/gitea:1.24 (1.24.7) and codeberg.org/forgejo/forgejo:15.0.11 on one volume. ADR-0034 says such platforms aren't migrated in place; nothing in the CLI stops the bootstrap.
Expected result
urbex bootstrap on a platform whose forge is still Gitea refuses before changing anything (non-zero exit), saying the platform comes from 0.1.0, why, and how to move on: destroy the environments, urbex teardown, urbex bootstrap, back up named volumes first; or stay on 0.1.0.
Activity
docs(changelog): Forgejo's breaking change with bootstrap's refusal (#…