-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Gitea fails to start after #13439 reverted db migration #13440
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Please update the version on the database manually. |
Gitea now runs fine again 🚀 |
I can confirm the manual downgrade. We are running gitea now for long time and appreciate it. Can you recommend a migration path from gitea:latest docker container to the stable release? |
as |
...unless you are using watchtower or some other means to track images updates. You are right, stopping this behavior and waiting for the release to reach or exceed todays :latest version is probably the first migration step. |
We are sorry if you have lost columns "commit_sha", "patch" of comments which type = 21 because of #13217 , if not, that's lucky. |
I am not aware of that, and there's always backups to restore from if yes. |
Gitea Version: 1.14.0+dev-157-g35cc82abbf
andGitea Version: 1.14.0+dev-158-gc178a36438
git version 2.29.2.299.gdc1121823c
Description
Moving from pre-#13439 to after #13439 fails to migrate the db and Gitea does not start.
The revert in the PR causes Gitea to say this
Had to rollback to a commit prior to the subject PR being merged.
The text was updated successfully, but these errors were encountered: