You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to run some manual SQL for preparing the tables for supertokens-core5.0.
Connect to the database with your favorite tool and run the following SQL query:
Supertokens 4.6 → 5.0 Upgrade Protocol
Supertokens 4.6 to 5.0 has breaking changes, which require careful granular steps for upgrading and deploying GraphQL Hive.
Rollout Plan
1. Make sure all CDI API calls use cdi-version 2.20
We have some manual fetch calls (integration-tests and API/server).
We need to make sure they use the latest supported cdi-version of 4.6 and 5.0.
Implementation PR:
#2604
Docker Hash to Deploy to Production:
9e935d2e068a41b7cf217fa27db4e9b3d8c5acc1
2. Prepare Database (pre step 3)
We need to run some manual SQL for preparing the tables for
supertokens-core
5.0
.Connect to the database with your favorite tool and run the following SQL query:
3. Bump and deploy
supertokens-postgresql:5.0
Bump and deploy
registry.supertokens.io/supertokens/supertokens-postgresql:5.0
Implementation PR:
#2602
Docker Hash to Deploy to Production:
58bc873526f087b849283294c8d9ce685536030f
4. Cleanup Database (post step 3)
We need to run some manual SQL for
supertokens-core
5.0
.Connect to the database with your favorite tool and run the following SQL query:
5. Upgrade used Supertokens CDI versions and SDKs
Upgrade cdi-version 2.20.0 —> 2.21.0
After we rolled out the new supertokens version we can adjust our code to now use CDI
2.21
instead of2.20
.supertokens-node
to **14.1.3 (**https://github.com/supertokens/supertokens-node/blob/master/CHANGELOG.md#1413---2023-07-03)fetch
calls (integration-tests and API/server)Implementation PR:
#2605
Docker Hash to Deploy to Production:
67abf74c90ecc3bbe28cb03c58cf785579f8767b
Issues
Random error on API (server service) after upgrading
Solution:
We did not pin an HTTP call to a
cdi-version
(709fc63)The text was updated successfully, but these errors were encountered: