Question: How to upgrade from 0.31 to latest

[stupkad]

Hi,

first, I wish everyone a great start into a hopefully very sucessful year 2025!

we are running a self hosted twenty instance, which works fine for us. In the upgrade guide, I did not find an information how to upgrade. Our current version is 0.31.0, currently the latest one is 0.35.0.

Do I have to follow the upgrade guide for each version (0.31.0 to 0.32.0, then 0.32.0 to 0.33.0, then 0.33.0 to 0.34.0 and finally 0.34.0 to 0.35.0)? Or can I skip all versions in between and upgrade directly from 0.31.0 to 0.35.0?

Thanks,
Dietmar

[BOHEUS]

Hi @stupkad, you have to follow the upgrade guide for each version like you wrote so from 0.31.0 to 0.32.0, then 0.32.0 to 0.33.0, then 0.33.0 to 0.34.0 and finally 0.34.0 to 0.35.0, I checked the docs and there's no information about that, so I'll add necessary information and create a PR

[FelixMalfait]

Yes this is very painful but that's the way to do it right now, sorry :(.
The modular structure of our application with a custom data model per workspace make it harder to build this that for a typical Saas.

That's something we plan to improve by end of Q1. @ehconitin will work on a way to auto trigger upgrade commands upon deploy, the same way we trigger typeorm database migrations

[stupkad]

Thanks for your answeres. I successfully upgraded my installation. Quite tricky, because twentycrm/twenty-postgres:0.33 (and later) does not exist. Perhaps there should be a hint about that (and the new spilo image). twentycrm/twenty-postgres:latest works fine.

I one command tjhe is a typo docker-compose up -d shoud be docker compose up -d (Note the dash)

[FelixMalfait]

Ah yes we should migrate from docker-compose to docker compose indeed, I'll create an issue thanks!

For the DB yes we changed and migrated to a new db called twenty-postgres-spilo, but you don't need to switch, for now there's nothing that prevents the app from working by staying on twenty-postgres