GitLab upgrade path on Cloudron (17.4.2 → latest)

[abo_shahad]

Hello everyone,

I’m running GitLab 17.4.2 on Cloudron, and I can see that the latest available version in the App Store is 18.8.

Before proceeding with the update, I’d like to clarify how Cloudron handles major GitLab upgrades:
• When updating GitLab via Cloudron, does it upgrade directly to the latest version (e.g. 17.4.2 → 18.8)?
• Or does Cloudron internally handle sequential version upgrades to satisfy GitLab’s upgrade path requirements?

I’m aware that on self-managed GitLab installations, skipping certain major versions is not recommended, so I want to make sure Cloudron’s packaging and migration process safely handles this.

Any clarification from the Cloudron team or users who’ve upgraded GitLab across major versions would be appreciated.

Thanks in advance!

[james]

Hello @abo_shahad and welcome to the Cloudrom Forum

@abo_shahad said in GitLab upgrade path on Cloudron (17.4.2 → latest):

When updating GitLab via Cloudron, does it upgrade directly to the latest version (e.g. 17.4.2 → 18.8)?

Since you are running GitLab version 17.4.2 this is the Cloudron package version 1.95.1.
No. Cloudron does not skip from a current version to the latest since this could cause some major issues.
You are ~40 versions behind, this means, you will have to update your GitLab app ~40 times.

May I ask why your GitLab app is so far behind? Did you disable automatic updated for the app?

---

@abo_shahad said in GitLab upgrade path on Cloudron (17.4.2 → latest):

Or does Cloudron internally handle sequential version upgrades to satisfy GitLab’s upgrade path requirements?

Yes.
This is the case for all Cloudron apps. All apps need be updated sequentially.
Also, if you did not know, each Cloudron app update goes through an automatic life-cycle test and a manual review process that ensures that each app update should cause no issues before it gets shipped to everyone.

---

@abo_shahad said in GitLab upgrade path on Cloudron (17.4.2 → latest):

I’m aware that on self-managed GitLab installations, skipping certain major versions is not recommended, so I want to make sure Cloudron’s packaging and migration process safely handles this.

That is what Cloudron does for every app.
The user, you, should not have to worry about app updates.
And even if an app update fails, a quick backup restore to the backup created before the update saves you a lot of headaches.

---

@abo_shahad said in GitLab upgrade path on Cloudron (17.4.2 → latest):

Any clarification from the Cloudron team or users who’ve upgraded GitLab across major versions would be appreciated.

Since the Cloudron GitLab https://git.cloudron.io/ is also running on Cloudron, we are doing the same GitLab app update as you are.
If something were wrong, we would have this issue on our own hands immediately.

---

If you have any more questions, please never hesitate to ask.

[jdaviescoates]

Also, to speed up your auto updates you could change your auto updates to every hour and then just wait a couple of days for it to get through them all