CloudQuery key use-cases and features:
This release introduced a breaking change to our protocol, this requires upgrading all providers to their latest version, moreover, if you get any migration issues, please make sure to drop your prior schema or start CloudQuery with a clean database.
CloudQuery introduced migrations many versions ago, allowing us to create diff changes across multiple versions, creating an easy update path for our users to upgrade their provider schemas.
Unfortunately, this wasn’t robust enough when supporting new databases and dialects such as TimescaleDB. So we set to upgrade our migration protocol so newer upgrades of your CloudQuery will be smoother and cause fewer issues.
This feature allows you to easily support changes across any dialect you use if it's TimescaleDB for History or vanilla Postgres. Moreover, it the opens path to support different databases and dialects in the future so stay tuned! or even better ping us on flavour you might want us to support next!
As always more resources, providers, policies, improved stability, and support for a new feature called Query On Demand. If you would like to influence our roadmap feel free to open an issue on our Github or Discord!