Share feedback, ideas and get community help

Updated 2 months ago

Update version from 2.24 to 3.0

At a glance

The community member is using version 2.24.1 of a software and wants to update to the latest version 3.0.1. They are using a Docker image and want to know if they can just update the image or if they need to make any other changes, such as to environment variables. The community members in the comments suggest checking the breaking changes documentation first, and discuss the database migration process. Some community members indicate that running db:migrate should be safe and necessary, while others note that the Docker image automatically applies the migration, so no manual action is required. The community members are not using the Docker image and have manually installed the software, so they need to run the migration manually.

Useful resources
I am currently using version 2.24.1 and intend to update to latest (3.0.1).
I use docker image. Can I just update the image and call it the day? Do I have to make changes to env variables and /or anything else? I could not find documentation on this.
B
J
K
9 comments
@Baptiste , I'm in the same boat as above where I'm upgrading from v2.3 --> v3.1.1. Only question I have is the database portion; do I still need to execute db:migrate or can I use the existing schema? If I execute the db:migrate, will it be backward compatible with v2.3.
db:migrate should always be safe to apply, it shouldn't break anything.
And yes you always need to run db:migrate
so I'm trying to run bun db:migrate and getting script not found. Im running in the main directory where I also execute bun install and bunx turbo build --filter=builder... --filter=viewer...
The docker image automatically applies the migration
You should not have to do anything manually
we are not using the docker image; we manually installed this
How did you resolve that?
Add a reply
Sign up and join the conversation on Discord