1.31 upgrade path
Apologies if this has been posted elsewhere - looking to upgrade from 1.31. I would normally just do incremental upgrades from 1.31 to 1.4, then 1.5, then 1.6, then 1.67, but want to validate and verify.
Is there any guide for this? I'm self-hosting this in Portainer.
3 Replies
Hey @Ergodyc,
Yes you got the main idea, you can follow the general guidelines from https://twenty.com/developers/section/self-hosting/upgrade-guide
Be sure to restart your container between each upgrade
Do be 100% sure an upgrade has been successful you can double check your workspace version is set to the expected upgraded version in database as
core schema workspace table version col
You can already double check that your workspace is at the expected currently installed twenty version before proceeding to your instance upgrade
Also be sure to at least make a dump of the very initial state before starting the upgrade just in case
Please always upgrade to the latest minor patch or directly consuming the major.minor entries the docker hub
Also no need to upgrade between patch version
1.6.6 and 1.6.7 are the same version in the end in term of upgrade/migration matterThank you. As i'll be doing this via Portainer, i presume i don't need to change the DB image (postgres 16) or redis (8.2) during the upgrades?
No need to touch to postgres and redis indeed