DevOps Demon
11/06/2025, 10:06 AMrahul1
11/06/2025, 9:50 PMcody
11/06/2025, 10:04 PM-- Run this SQL query on your Postgres database
UPDATE "DatabaseMigration" SET "dataVersion"=31;
Option 2: API Command
In version 3.3.0, we also added an API endpoint to set the data version. You can use this endpoint to set the data version to 1.
# Get an auth token
export AUTH_TOKEN=$(npx medplum token)
# Use curl to set the data version
curl -X POST \
-H "Authorization: Bearer $AUTH_TOKEN" \
-H "Content-Type: application/json" \
https://api.medplum.com/admin/super/setdataversion \
-d '{ "dataVersion": 31 }'
After using either option, you can proceed directly to upgrading to version 5.0.0.DevOps Demon
11/07/2025, 2:54 AMDevOps Demon
11/07/2025, 2:57 AMDevOps Demon
11/07/2025, 6:41 AMcody
11/07/2025, 6:48 PMapp and server are running Medplum version 5.0.0? You can confirm the app version in the top-right menu. You can confirm the server version using the /healthchecek endpoint
2. Is your bot using runtime version vmcontext or awslambda?
3. If using awslambda, have you recently deployed the Medplum bot lambda layer? https://www.medplum.com/docs/bots/bot-lambda-layerDevOps Demon
11/10/2025, 5:20 AMVMCONTEXT and our infrastructure is set up on GCP not AWS. So awslambdalayer is out of picture.Ian Plunkett
11/18/2025, 5:35 PMDevOps Demon
11/18/2025, 5:40 PMDevOps Demon
11/18/2025, 5:40 PMAceOfSpades
11/21/2025, 5:43 PMnathan-watkins-unityai
11/21/2025, 6:54 PMAceOfSpades
11/21/2025, 8:10 PMDevOps Demon
11/22/2025, 4:30 AM