But for anyone else watching:
If we have versions up to 1.14.7 and 1.15.2.
and your current version is 1.14.2
just update to 1.15.2 or do 1.14.7 then 1.15.2 only.
DO NOT DO 1.14.3, ..., 1.14.7, 1.15.0, 1.15.1, 1.15.2
If you are on 1.14.3-1.14.6 because there was a bug in the dump command in these versions: if you backup your db using dump then you need to migrate to 1.14.7 to get a dump before you upgrade to 1.15 - but even then do not do 1.14.3,1.14.4,1.14.5,1.14.6,1.14.7 just go straight to 1.14.7 - make the dump and thence straight to 1.15.2.
We really want to avoid this 🙃 :
As a result, I ended up having to export all repos, start from scratch with a stable version of gitea, recreate/reconfigure all orgs and settings, reimport all repos, recreate all users/permissions, and reconfigure all repos. We lost all of our pr history
```
But for anyone else watching:
If we have versions up to 1.14.7 and 1.15.2.
and your current version is 1.14.2
just update to 1.15.2 or do 1.14.7 then 1.15.2 only.
DO NOT DO 1.14.3, ..., 1.14.7, 1.15.0, 1.15.1, 1.15.2
If you are on 1.14.3-1.14.6 because there was a bug in the dump command in these versions: if you backup your db using dump then you need to migrate to 1.14.7 to get a dump before you upgrade to 1.15 - but even then do not do 1.14.3,1.14.4,1.14.5,1.14.6,1.14.7 just go straight to 1.14.7 - make the dump and thence straight to 1.15.2.
```
We really want to avoid this 🙃 :
```
As a result, I ended up having to export all repos, start from scratch with a stable version of gitea, recreate/reconfigure all orgs and settings, reimport all repos, recreate all users/permissions, and reconfigure all repos. We lost all of our pr history
```
from https://github.com/go-gitea/gitea/issues/16828
We really want to avoid this 🙃 :
from https://github.com/go-gitea/gitea/issues/16828
We are not using a version which has a bug in
gitea dumpcommand so that is good for usUseful: https://peterbabic.dev/blog/upgrading-gitea-to-1-15/
We have upgraded!