Platform compatibility

Stub versions remain stable while BusinessStub grows.

BusinessStub separates API, generated Worker, import, editor schema, browser widget, database, and Cloudflare runtime versions. Existing integrations remain available until they complete an explicit deprecation and sunset process.

Current contracts

Legacy v0: existing unversioned stub APIs remain supported for registered older deployments.
API v1: new integrations use /api/v1/stubs/<slug>/....
Import v1: remains readable, and fields absent from old bundles are preserved during updates.
Import v2: records runtime/API versions, capabilities, provenance, and exact widget releases.
Widgets: production sites pin immutable semantic versions rather than mutable shared URLs.

Each accepted current import registers a deployment record. A platform admin marks the active release verified only after its canary check passes; earlier release history remains intact.

Deprecation and sunset

Legacy means supported but unavailable for new integrations. Deprecation begins only after a successor and migration path are available. Deprecated responses advertise the standard Deprecation header and migration documentation. A Sunset header appears only after a shutdown date is approved.

BusinessStub does not sunset a contract while registered active deployments still depend on it. Fleet inventory and recent version telemetry must show that migration is complete.

What stub operators should do

Existing sites can continue using their current integration. New deployments should use the current authoring template, versioned upstream paths, BusinessStub-Integration-Version: 1, and immutable widget URLs. BusinessStub will coordinate any required migration before an old contract reaches sunset.