Hi @kapa.ai, when I do docker compose start to re deploy Airbyte after changing a .env parameter, my sources / destinations versions update are erased and go back to the version the first time I deployed Airbyte I am using Airbyte 0.50.4 When doing docker compose start, • Postgres source goes back from 3.1.9 to 2.0.33 • S3 destination goes back from 0.5.1 to 0.4.1 This creates bugs on my connectors Can you please tell me why it does this and is there a workaround?

Hmm, I don't know enough to give you a confident answer yet. However, based on the information provided, it seems like there might be an issue with how your environment is set up or how the docker compose command is being executed. In the [documentation](https://docs.airbyte.com/operator-guides/upgrading-airbyte/), it is mentioned that you need to turn off Airbyte and upgrade the docker instance to a new version. If you're running Airbyte from a cloned version of the Airbyte GitHub repo, you should use

git pull

to get the most recent stable version. If you're running Airbyte from downloaded

docker-compose.yaml

and

.env

files without a GitHub repo, you should run

wget <https://raw.githubusercontent.com/airbytehq/airbyte/master/run-ab-platform.sh>

to download the installation script. After that, you need to remove the previous local

docker-compose.yaml

and

.env

files and bring Airbyte back online. If you're still facing issues, it would be best to check the [Airbyte documentation](https://docs.airbyte.com/) or ask for help in the [Airbyte community](https://discuss.airbyte.io/).

So @kapa.ai, is this issue solved by Airbyte later versions ? if yes, which one ?

A message from kapa.ai