Repository navigation
v0.4.3
Superbee 0.4.3 adds links between bundles with declared dependencies, offline integration authoring with explicitly consented local sources and tool operations, local full-text search, typed Kind fields, and safer recipe installation and evolution.
npm install -g superbee
superbee setupRead the docs: Superbee 0.4.3 release notes · Build on Superbee · Author an integration · Link across bundles
What changed
- Links between bundles. A bundle can declare its own identity (
bundle id set) and its dependencies on other bundles (deps add|remove|list). Documents link across bundles with qualifiedokf://links (link add --bundle), andstatus --with-depsandlink show --with-depsreport how each qualified link resolves. - Integration authoring. Recipes can declare Connectors.
recipe validatechecks a recipe and its Connectors offline.source plugin register,source bind,source run, andsource testbring records from another system into a local or Git bundle only after explicit private consent; recorded tests never run live. Finite local snapshots ingest through the same reconciliation. The GitHub integration builds from superbee-plugins commit0b9241c7. - Local tool operations.
op register|bind|run --localruns an explicitly registered and consented tool and exports its evidence. - Search.
searchfinds documents by text in a local bundle, and the local MCP server exposes the same search. - Typed Kind fields. Kind conventions can declare field value types (
fields.types). Writes validate and convert typed input, and owned list fields support replace-all, unset, and compare. - Safer recipes. Installation runs a read-only structural preflight before any write. Evolution converges regardless of list order and line endings, adopts recipe-owned References safely, accepts additive inbound expectations and proven field description replacements, and supports scoped declaration deprecation and retirement.
statusreports Kind coverage and validates the target Kind of qualified links. - Hosted checkouts sync ordinary files, resolve blob conflicts with keep or take, and send and read workspace notifications with
notifyandinbox. - One write policy. Body replacement data-loss guards and document replacement guards now live in shared core policy, so the CLI and the reference server refuse the same unsafe writes.
Compatibility
Existing OKF bundle editions and document workflows are retained; bundle identity, dependency declarations, and typed Kind fields are optional and additive. Node ^22.14.0 || ^24.0.0 || ^26.0.0 on macOS or Linux; WSL2 follows Linux, and native Windows npm execution remains excluded. No bundle migration is needed.
Full Changelog: v0.4.2...v0.4.3