Unable to update from an old version

Hello, i recently saw than my version of twenty was pretty old (v0.50), so i pulled the latest image and after that, a lot of errors appeared, so i've gone back to my old version and everything was ok, i tried to update from 0.50 to 0.51 and it worked ! But i can"t figure out how to go from 0.51 to 0.52 without error, thank you for you're help ! (i'm french btw so sorry for my english)
24 Replies
Prastoin
Prastoin2w ago
Hello Evan, indeed you need to incrementally upgrade your twenty instance Could you please share the errors you're facing ?
Evan C.
Evan C.OP2w ago
Hello ! Ok don't move , i gonna do some screen 🙂 So, the initial version where everything work for me is 0.50.5 and when i go to v0.51 , i have this
Evan C.
Evan C.OP2w ago
No description
Prastoin
Prastoin2w ago
Have you followed the upgrade guide ? https://twenty.com/developers/section/self-hosting/upgrade-guide#v0.50-to-v0.51 Looks like you did not run migrations nor upgrade
Evan C.
Evan C.OP2w ago
ok thank you , i gonna try this Hi, i try to use the guide, but i have this error when i go from 0.51 to 0.52
Evan C.
Evan C.OP2w ago
No description
Prastoin
Prastoin2w ago
Please restore a backup Of 0.51 version Seems like you're using the one that you tried to migrate to latest version Please review your workspace version in db core.workspace.version
Evan C.
Evan C.OP2w ago
It was the backup from 0.50 that I tried to update. I'm going to check the version, don't move.
Prastoin
Prastoin2w ago
Are you building your own twenty image or using official ones from docker hub ?
Evan C.
Evan C.OP2w ago
0.50.5 the version in database I use the image from docker hub With the compose on your website i thougt i did the update well Because in the front (before the error between v0.51 and v0.52) i had the v0.51 version in my admin panel
Prastoin
Prastoin2w ago
Looks like migration from 0.50 to 0.51 failed By share failing upgrade logs What's the complexity of your twenty instance ? If it's very basic the most straigthforwrad solution might be to export everything rows as csv and re-import them in a latest fresh install You would still have to manually re-define your data models though
Evan C.
Evan C.OP2w ago
mhmmmm i see, im gonna retry the update betwenn 0.50 and 0.51 Our instance start to be pretty complexe, i would like to keep it if possible ahah Ok, just to be clear before try it again, i need to change my version in .env file then i recreate the container and after that i do the yarn on the server container ? its that ? ok so now i succesfully updated from v0.51 to v0.52 BUT new error🥲 After updating to v0.53 i'd check if the core.version was right and it was stuck on v0.52 even if in the guide it said than from the v0.53 teh migration will be auto, sooo i tried to migrate myself like with v0.51 and v0.52 and after the migration upgrade i have that
Evan C.
Evan C.OP2w ago
No description
Evan C.
Evan C.OP2w ago
(sorry to bother you with that but the 1.0 of twenty seems so cool and we really want to use it !)
Prastoin
Prastoin2w ago
You should never install dev dependencies on your production container Production dependencies are already shiped withint the image, you need to run the migrate an upgrade command manually until version 0.53 Starting from 0.53 it's done at the bootstrap of your twenty-server Please review migrate and upgrade logs at the beginning of your container logs instance
Evan C.
Evan C.OP2w ago
Same error than my manual upgrade :
No description
Evan C.
Evan C.OP2w ago
What is this metadata field ?
Prastoin
Prastoin2w ago
What's your exact 0.52 tag in your .env please Is it patch agnostical or if not what patch
Evan C.
Evan C.OP2w ago
im in v0.53 now because the v0.52 upgrade goes well , but it was the v0.52.11 version in core.version and on the .env it was v0.52
Prastoin
Prastoin2w ago
Ok cool @thomast have you ever heard of such an issue around 0.52 ? Would manually define the workflows settings be sustainable through time or should this have been done by prior version commands ? Ok after some investigations this seems unrelated to workflows in the end, but rather to relation field metadata refactor ( workflow is relation field in the end ) Searching for existing commands in these tags My hunch is that you missed prior versions upgrades
Evan C.
Evan C.OP2w ago
before the v0.50 ? or during my journey of upgrade from v0.50 ? x)
Prastoin
Prastoin2w ago
Before I guess
Evan C.
Evan C.OP2w ago
ouch im gonna try to investigate, i come back if i succed or not
Prastoin
Prastoin2w ago
upgrade:0-52:migrate-relations-to-field-metadata Still in your current instance please try running yarn command:prod upgrade:0-52:migrate-relations-to-field-metadata 0.52 commands are available in 0.53 too

Did you find this page helpful?