v0.4.0

Add typed destinations alongside pull syncs. Integrations can now receive host-prepared batches of upserts and optional deletions through runDestinationBatch, using the same connection and SDK provider.

• Validate complete destination batches before execution, including record schemas, primary keys, duplicate identities, and size limits.
• Preserve cancellation through asynchronous cleanup and reject coercion anywhere in destination key schemas.
• Add a mocked destination replay example and document field mapping, delivery, and replay responsibilities.

Breaking changes and compatibility

New builds target manifest v4 and host contract v4, including pull-only integrations. Upgrade execution hosts before loading newly built artifacts. Compatibility inventories now use format v3.

Existing v3 pull artifacts and source remain supported. The process protocol remains v1. Destination execution is available through the embedded host API; destination CLI and process-protocol operations are not included in this release.

The SDK validates and executes destination batches; the host owns change detection, mapping, ordering, durable progress, and replay. Destinations must support safe repeated upserts and deletions.

Full Changelog: v0.3.0...v0.4.0

v0.3.0

Beetl Connect SDK 0.3.0 introduces keyed generator syncs and a function-based host API. Requires Node.js 24.2 or newer.

Breaking changes

• Define syncs as a keyed object and implement each sync as an async generator that yields record batches.
• Import provider, execution, and OAuth APIs from @beetlio/connect/host. The /local-host and /oauth entry points have been removed.
• New artifacts use manifest v3 and host contract v3. Older artifacts are rejected before import; migrate integrations and rebuild them. The process protocol remains v1.

See the compatibility contract and updated examples before upgrading.

Improvements and fixes

• Shared provider functions handle authentication, OAuth preparation and refresh, origin restrictions, and retries.
• Authentication and cleanup failures remain visible, and connection-level retry policies are honored.
• Windows integration builds correctly match TypeScript source paths.
• Installed-package checks reuse compatibility fixtures and preserve frozen artifact provenance.
• CI covers Node.js 24.2, 24, and 26 on Linux, with macOS and Windows package checks. Dependency audits, CodeQL, and Dependabot are configured.

Documentation

The release workflow stages @beetlio/connect@0.3.0 on npm. It becomes available after maintainer approval on npm.