Individual source connector version in Airbyte 0.50.7 is rolling back after a few hours despite incrementing the version number. How to fix this?
Upgrading an individual source connector does not persist. While the version number is incremented, the version rollsback after a few hours. How do I fix this on 0.50.7?
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want to access the original thread.
Based on the information provided in the extracts, it seems like there have been issues with upgrading source connectors in Airbyte version 0.50.7. This issue has been reported on GitHub here and here. One workaround that was mentioned is to use docker-compose down and docker-compose up again, which seemed to resolve the upgrading issue for some users. However, it’s important to note that these issues might have been resolved in later versions of Airbyte. Upgrading to the latest version of Airbyte might help resolve this issue. If you continue to face issues, it would be helpful to provide more information or logs for further diagnosis. You can also reach out to the Airbyte community on their forum or Slack for more assistance.
Are you on OSS or Cloud? I don’t think that’s the intended behavior 
Whoa, 0.50.7 is from July 2023. I think this might be already solved — we fixed quite a lot of things since then.
Any chance you can upgrade to a recent version and see if you can reproduce the problem?