CloudQuery SQLite v2.14.10 - Plugin SDK Update

CloudQuery plugins-destination-sqlite-v2.14.10 was published on June 19, 2026. The SQLite destination release is a small maintenance cut: its listed bug fix updates github.com/cloudquery/plugin-sdk/v4 to v4.95.3, with no prerelease flag and no migration note in the GitHub text.

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

The release notes contain one change, not a feature batch. CloudQuery updated the module dependency github.com/cloudquery/plugin-sdk/v4 to v4.95.3, tracked in issue #22946 and landed as commit b9aac1f. For data teams using SQLite as a local destination, that makes this release mainly about keeping the destination plugin aligned with the current CloudQuery SDK branch.

That matters because destination plugins sit on shared SDK behavior for table handling, write paths, diagnostics, and plugin protocol integration. The notes do not list a SQLite schema change, a config key change, or a new CLI option. Treat it as dependency hygiene unless your environment has pinned plugin binaries or validates exact module graphs.

The release name is plugins-destination-sqlite: v2.14.10, so the scope is the SQLite destination package inside cloudquery/cloudquery. The notes do not claim broader CloudQuery core changes. That distinction is useful when you run several destinations in the same estate and need to decide whether this tag belongs in a standard connector refresh or a wider platform test window.

SQLite destinations are common for small extracts, local inspection, reproducible test fixtures, and CI style data snapshots. A plugin SDK bump can still be relevant in those workflows because the SDK is part of the runtime contract between source plugins, transformations, and destination writes. The release does not say that users need to rewrite config, rebuild tables, or change how state is stored.

The practical test is straightforward. Install or pin plugins-destination-sqlite-v2.14.10, run an existing sync against a small dataset, then compare the destination file shape and row counts against the prior v2.14.9 plugin. The upstream compare target in the notes is plugins-destination-sqlite-v2.14.9...plugins-destination-sqlite-v2.14.10, which reinforces the narrow scope.

If your pipeline builds images with CloudQuery plugins baked in, this release should go through the same image rebuild and smoke sync path as any other plugin update. If your jobs download plugins at runtime, check cache behavior and artifact pinning before changing production runs. Nothing in the notes suggests an urgent security issue or a breaking migration, but silent connector drift is still a source of bad data in scheduled ELT.

There is no published note for new SQLite options, partition behavior, type mapping changes, WAL settings, transaction batching, or query cache behavior. There is also no prerelease marker. That means the safest reading is limited maintenance, not a data model event.

This is still worth recording because CloudQuery destination releases are the unit most operators actually pin. A short release with one dependency line can affect repeatability if different workers resolve different plugin versions. Keep the version tag visible in job definitions, image labels, or deployment metadata so a failed sync can be traced back to the exact plugin binary.