Upgrading GitLab Community Edition (GitLab-CE) can be a bit tricky. In many cases, a direct upgrade isn’t feasible due to dependency constraints and version compatibility. Several components may require incremental upgrades, and GitLab is no exception.
In this video, I’ll demonstrate how to use the apt-mark utility—a tool I wish I had discovered years ago. Before upgrading GitLab-CE to the latest version, I used apt-mark hold to prevent the package from being unintentionally upgraded during system updates, which could potentially break the application.
I’ll walk through how to place a hold on packages and how to remove that hold when you're ready to proceed. I’ll also introduce the following resource:
🔗 GitLab Upgrade Path Tool This tool helps ensure GitLab is upgraded correctly by guiding you through the supported version transition steps.
On this page of the site you can watch the video online Upgrading GitLab CE: Avoiding Pitfalls with apt-mark with a duration of hours minute second in good quality, which was uploaded by the user TerrorPUP 18 October 2025, share the link with friends and acquaintances, this video has already been watched 125 times on youtube and it was liked by 6 viewers. Enjoy your viewing!