Release and documentation status
Current Fabric Harness package versions, Node.js requirements, documentation scope, and migration links.
This site documents the currently published Fabric Harness contracts. Package families are
versioned independently, so matching major numbers are not a compatibility guarantee. New projects
should be created with @fabric-harness/cli@latest, which pins a compatible set of packages.
Published does not mean that every optional managed provider ran in the latest protected suite. Use Validation status to separate deterministic contract coverage, credentialed provider evidence, deployment conformance, and exact-package certification.
| Package | Stable version | Node.js engine | Purpose |
|---|---|---|---|
@fabric-harness/sdk | 6.1.0 | >=20.18.0 | Portable SDK and public agent contracts |
@fabric-harness/cli | 6.6.1 | >=20.18.0 | Scaffolding, local runs, builds, and deployment |
@fabric-harness/node | 6.1.0 | >=20.18.0 | Node runtime and HTTP server |
@fabric-harness/databricks | 7.0.2 | >=22.0.0 | Databricks integration and deploy targets |
Runtime requirements
- Core minimum: Node.js 20.18 or newer for the SDK, CLI, Node runtime, and most optional integrations.
- Recommended: Node.js 22 LTS for new projects and framework development.
- Databricks: Node.js 22 or newer is required by
@fabric-harness/databricks. - Feature-specific: APIs that depend on the platform
WebSocketor built-innode:sqlitemay require a sufficiently recent Node 22 release. The relevant feature page calls this out.
The root monorepo uses Node.js 22 or newer for maintenance and release work. That contributor requirement is stricter than the minimum engine supported by the core published packages.
Documentation version
Unqualified guides on this site describe the stable package versions shown above. Historical version numbers appear only in clearly labeled migration or certification records. Databricks evidence pages identify the exact package used for a protected workspace run because that evidence does not automatically transfer to another release.
For a project you already have, run:
npx fh --version
npx fh capabilities --json
npm view @fabric-harness/sdk version engines --jsonUse the compatibility contract to negotiate behavior rather than assuming that a version number alone proves a feature is present.
Upgrading
- Install or update Fabric Harness
- Migrate from legacy agent APIs
- Check CLI capability compatibility
- Review Databricks compatibility evidence
- Review current client-pilot validation evidence
Each package name in the table links to its public npm release history. Detailed, commit-level changelogs are maintained in the restricted source repository and are available to authorized customers and partners; see source access.