Releases and support
Published versions, alpha limits, licences, and upgrade policy.
These pages target registry packages checked on 16 September 2026. Pin versions in your application's lockfile; the current main branch can contain APIs that have not shipped.
| Artifact | Published version used here | Maturity |
|---|---|---|
@caveman-ai/sdk | 1.1.0 | Thin client and middleware runtime client |
caveman-sdk | 1.1.0 | Thin client and sync/async middleware runtime clients |
@caveman-ai/middleware | 0.1.0-alpha.2 | Alpha native adapters |
caveman-middleware | 0.1.0a1 | Alpha native adapters |
@caveman-ai/cli | 1.3.4 | Installer used by these examples |
| Signed runtime companions | bin-v1.1.7 | Runtime used for real Engine validation |
The installed signed runtime reported runtime_build: "dev" in capabilities during validation. Preserve the installer manifest and release asset identity; that field alone is not enough to identify this release.
Source changes are not releases#
SDK 1.1.0 exposes strict ready(), final decision reports, and recovery. It does not expose preflight(). Unreleased development work adds preflight diagnostics and tighter compatibility evidence, but no package release was made for that work during this documentation refresh.
Do not import @caveman-ai/middleware/compatibility from published 0.1.0-alpha.2. That subpath and source fields separating exact test pins from supported ranges are candidate changes. The compatibility page describes the published artifacts and labels source-only evidence separately.
Licences#
The thin SDK and middleware adapters are MIT. The separate Agent SDK has its own licence and is not the same package. The runtime includes the Engine, whose BSL terms are separate from the client licence. First-party self-hosted use and relevant hosted, managed, or embedded offerings must be assessed against the actual Additional Use Grant and commercial terms, not the npm package badge.
Read LICENSING.md, the MIT licence, and the Engine licence. See licensing for the public overview and commercial contact path. Check the licences shipped with your pinned artifacts when upgrading.
Upgrade policy#
Treat alpha upgrades as potentially breaking even within the same broad accepted framework range. Pin package/runtime/framework versions, keep a known-good lockfile, and test upgrades in a separate environment. Re-run the deterministic quickstart, check the final decisions, then evaluate representative provider workloads and recovery before rollout.
Accepted ranges are guards, not proof of every version in the range. Public source tests, package metadata, and local documentation checks have different evidence levels. No blanket production certification, edge-platform support, or guarantee of task quality is implied.
Support and known limits#
File reproducible issues in the public Caveman issue tracker. Follow releases and the package release history. These alpha guides do not promise an SLA or a deprecation window.
Known limits include narrow eligible content, explicit recovery ownership, expiring scopes, stateful recovery storage, metadata-dependent TypeScript version detection, incompatible Python dependency combinations, and provider-dependent streaming usage. Optional paid examples were not executed for this release of the docs. Secondary adapters have source and import evidence as documented; that is not a complete real-provider evaluation of every family.
Include language, OS, package and runtime versions, framework lockfile, adapter entrypoint, mode, sanitized capability summary, final decision reason, and a minimal deterministic reproducer in an issue. Omit credentials, original prompts/tool data, bearer tokens, and live recovery handles.