Interesting, thanks for the heads up - We didn't have any issues while I was there and probably would just restore if we needed to, but nice to know the footguns.

interesting, this isn't my experience. I've been running a gitlab instance for about 300 people for about 7 years now. :\

To be fair though I'm using docker and watchtowerr to keep it updated, there was 1 time where I had to use an older docker image because the latest wasn't working.

For those like me who went familiar with it: https://containrrr.dev/watchtower/

This happened to me exactly _once_ in the last three years of successful monthly update on our self-hosted GitLab instance. I got an error because the backup script expected a folder where no folder was. Updating GitLab is a breeze!

It’s incredibly dumb that it allows you to start the next upgrade before the background migrations finish.

Not unrecoverable though, so saying you need to worry about it may be a bit too alarmist.