mirror of
https://github.com/RayLabsHQ/gitea-mirror.git
synced 2026-04-25 07:15:57 +03:00
[GH-ISSUE #97] database migration failing after update to 3.7.2 #51
Labels
No labels
bug
documentation
enhancement
help wanted
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/gitea-mirror#51
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @CrazyWolf13 on GitHub (Sep 14, 2025).
Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/97
Originally assigned to: @arunavo4 on GitHub.
Hi @arunavo4
Got this error today after the upgrade, which seemed to go through successfully:
@arunavo4 commented on GitHub (Oct 1, 2025):
Hi @CrazyWolf13 thanks for flagging this, I have made a manual migration file fix that should take care of this issue. would be awesome if you can test the image before I merge it.
@CrazyWolf13 commented on GitHub (Oct 1, 2025):
@arunavo4 Thanks a lot!
Running this probably won't work as easy, as I run dockerless inside an LXC, could you tag this as a release but not tag as latest so I can push the gitea-mirror script to our community-scripts/ProxmoxVED (testing-repo) and manually pick the version and update like this?
@arunavo4 commented on GitHub (Oct 1, 2025):
Yea I can do that
@arunavo4 commented on GitHub (Oct 2, 2025):
@CrazyWolf13 https://github.com/RayLabsHQ/gitea-mirror/releases/tag/v3.8.1
@CrazyWolf13 commented on GitHub (Oct 2, 2025):
@arunavo4 thx worked beautifully!