Update from 1.7
Hello, I try to update from 1.7 to 1.8 and I have those errors. What ca I do to resolve this?
9 Replies
Thanks
And I have many lines like that in the logs
Hey @greg [iero] I don't see anything problematic here
What makes you think the upgrade failed ?
What's your workspace version in database ?
Hey @prastoin thanks for your reply
Those lines are unusual in the logs when I do updates:
codex-server | query: SELECT version();
codex-server | query: SELECT * FROM "information_schema"."tables" WHERE "table_schema" = 'core' AND "table_name" = '_typeorm_migrations'
codex-server | query: SELECT * FROM "core"."_typeorm_migrations" "_typeorm_migrations" ORDER BY "id" DESC
in the database, I see for my workspace :
-[ RECORD 1 ]---------------------+-----------------------------------------------------------------
id | 5bc2d041-8036-41ed-ba7a-a5514e1216d6
version | 1.8.2
So I'm good to update to next version?
You've upgraded successfully to 1.8.2
Everything's good here ! well done
Great thanks, thanks for your help, I continue to 1.9 🙂
If you're facing runtime issue please feel free to run a cache flush just in case
Ok cool !
There is no 1.9 ?
% curl -s https://hub.docker.com/v2/repositories/twentycrm/twenty/tags | jq -r '.results[].name' | head -20
v1.11
v1.11.0
v1.10.2
v1.10
v1.10.1
v1.10.0
v1.8.2
OK so I update to 1.10 directly
I have now this error:
codex-db | 2025-11-14 16:28:56.663 UTC [44] ERROR: constraint "FK_b3cc95732479f7a1337350c398f" for relation "view" already exists
codex-db | 2025-11-14 16:28:56.663 UTC [44] STATEMENT: ALTER TABLE "core"."view" ADD CONSTRAINT "FK_b3cc95732479f7a1337350c398f" FOREIGN KEY ("kanbanAggregateOperationFieldMetadataId") REFERENCES "core"."fieldMetadata"("id") ON DELETE CASCADE ON UPDATE NO ACTION
codex-server | query failed: ALTER TABLE "core"."view" ADD CONSTRAINT "FK_b3cc95732479f7a1337350c398f" FOREIGN KEY ("kanbanAggregateOperationFieldMetadataId") REFERENCES "core"."fieldMetadata"("id") ON DELETE CASCADE ON UPDATE NO ACTION
codex-server | error: error: constraint "FK_b3cc95732479f7a1337350c398f" for relation "view" already exists
I've done a cache:flush and it seemed to work.
I updated to 1.11, no alert.
finger crossed 😄
Is your workspace version in database to 1.11 ?
Yes there's no 1.9