denis256 notes and projects

CloudQuery released plugins-destination-postgresql-v8.15.0 on June 19, 2026, for the PostgreSQL destination plugin in cloudquery/cloudquery. The main change is support for Databricks Lakebase as a destination, with a plugin-sdk update underneath. This release is not marked as a prerelease.

The full release notes and downloads are on the GitHub release page.

Databricks Lakebase destination support

The user visible addition in v8.15.0 is Databricks Lakebase destination support, tracked in #22944 and shipped in commit 016717c. For teams already standardizing on Databricks, this makes the PostgreSQL destination plugin more relevant as a target for CloudQuery sync data.

The release notes do not list new config keys, CLI flags, auth modes, or migration steps for this feature. That matters for operators. Treat this release as support landing in the destination plugin, then validate the exact connection settings against the plugin docs and a test target before moving production syncs.

Lakebase is meant to behave like a Postgres compatible operational database. That makes it a natural fit for a PostgreSQL destination plugin, but compatibility claims still need practical checks. Schema creation, connection limits, write behavior, and permissions are the kind of details that usually decide whether a destination works cleanly in an existing pipeline.

PostgreSQL plugin scope

This tag is scoped to plugins-destination-postgresql-v8.15.0, not a broad CloudQuery platform release. That is useful when reading the change list. The release notes are about the PostgreSQL destination package, so there is no reason to assume changes to unrelated source plugins, destination plugins, or CloudQuery core behavior.

For users tracking CloudQuery plugin versions separately, the tag name is the important unit. Pinning or updating this destination should be handled the same way as other plugin updates in the deployment, with attention to the version of the destination plugin actually used by the sync job.

That narrow scope also helps rollback planning. If a Lakebase trial exposes connection or write issues, operators should be able to move only the PostgreSQL destination plugin back to the prior known version while leaving unrelated CloudQuery pieces alone.

The short release also means there is less noise to parse. There is one feature entry and one dependency entry. If your deployment does not need Databricks Lakebase, this is mostly a maintenance release unless the plugin-sdk update matters for your environment.

SDK update underneath

The bug fix section updates github.com/cloudquery/plugin-sdk/v4 to v4.95.3, tracked in #22946 and commit b9aac1f. The release notes classify this as a dependency update, not as a user facing behavior change.

That distinction is worth keeping. A plugin SDK bump can carry fixes or internal compatibility work, but this release note does not spell out a specific operator action. Read it as housekeeping unless your own tests show a behavior change in connection setup, batching, schema handling, or error reporting.

For production use, the practical check is simple. Run the same sync shape used in production against a safe target, especially if the destination handles large tables or frequent schema changes. If the output tables, errors, and timings look normal, the dependency bump should not need special handling.

Where to get it

• Release page: GitHub release page
• Repository: cloudquery/cloudquery
• Tag: plugins-destination-postgresql-v8.15.0