No, your upgrade path is wrong!
As per the docs: Upgrading GitLab | GitLab
13.1.11 -> latest 13.12.Z -> latest 14.0.Z -> 14.1.Z -> latest 14.Y.Z
since you are between 13.1.11 and 13.12.Z you need to upgrade to the latest available 13.12 release. You can search and find the latest 13.12.Z release here: gitlab/gitlab-ce - Packages · packages.gitlab.com which would be 13.12.10 right now. Then you need to go to latest 14.0.Z release, then latest 14.1.Z release, and then the latest 14.2.Z release. You can get an idea from their examples, shown in the screenshot below from the docs:
So, upgrade would be:
- Upgrade to 13.12.10
- Upgrade to 14.0.7
- Upgrade to 14.1.3
- Upgrade to 14.2.0
make sure after each upgrade that background migrations have finished and show
0 (zero) before continuing the next upgrade. Upgrading GitLab | GitLab
Please make sure to backup your server or create a snapshot before doing it, just in case it breaks during the upgrade process. This should be a normal procedure for any server upgrade.
Also, there is nothing stopping you to be extra careful, and upgrade from 13.4.1 via every single point release between here and 14.2.0. That’s almost if you like zero downtime upgrade. However, that would mean a lot of updates. I did that once going from 12.9.3 to 14.0 and it was about 40 - 80 upgrades in total. But at least I didn’t cause any issues if I missed a particular upgrade that had an important DB migration in it.