1.5.0 relative to 1.4.2. The remaining sections
cover 1.4.0 relative to 1.3.0. The stable release uses the npm latest
dist-tag; release candidates use next. Use an exact version when testing an
upgrade.
1.5.0
1.5.0 is the stable release and ships the same code as the 1.5.0-rc.1
candidate. Install it by exact version, together with its supporting packages,
which it pins to the same version:
createWiki SDK and MCP entry points are
unchanged. The storage interfaces are internal; this release does not add a
public storage-plugin API, hosted storage, a remote backend or role-based
permissions. Compatibility testing supports a drop-in upgrade but does not
guarantee byte-identical files, unchanged performance or identical behavior on
every platform. See ARCHITECTURE.md
for the design.
Prompt version v7. This release moves prompt provenance from v6 to v7
alongside the new --no-pages-limit extraction mode (SDK noPagesLimit: true).
Every newly generated page records v7, including pages from default runs
that do not use the new mode; default prompt wording is otherwise unchanged.
Upgrading alone does not recompile unchanged sources, but a source that needs
extraction again is extracted afresh rather than reusing a snapshot cached
under v6.
Converse provider. LLMWIKI_PROVIDER=converse is opt-in. Its
@aws-sdk/client-bedrock-runtime and @smithy/node-http-handler packages are
optional peer dependencies; install them only when you select Converse. See
provider setup.
MCP Registry. The registry entry io.github.atomicstrata/llmwiki is
published for 1.5.0 after the npm release. Release candidates do not update
the registry entry.
Back up a wiki you care about before upgrading, and reopen it with your actual
CLI or SDK integration before relying on the new release.
Claude provider correction
The Claude Agent SDK provider now isolates generation and extraction from personal/project filesystem settings andCLAUDE.md instructions. Existing
Claude login remains available. Use llmwiki environment variables for provider
configuration and compile --instructions <path> for explicit writing guidance.
Prompt provenance advances to v6. Upgrading alone does not recompile unchanged
sources: existing pages retain their recorded prompt version. A subsequent source
edit or explicit compile-instruction change can trigger regeneration; newly
generated concept pages then record v6. Use compile --review to inspect those
updates before approval.
What stays the same
Continue importingcreateWiki from llm-wiki-compiler for the standard SDK.
The standard CLI, workflow facade, builtin profile templates and legacy viewer
experiment input remain available. Scoped supporting packages are implementation
dependencies, not separately supported consumer entry points. Node 24 remains
the minimum, not a new requirement.
The extraction does not require migrating local workflows to an external
coordinator; the local engine retains run state between local invocations. See
SDK packages and ownership before changing dependencies.
Experimental source changes
Artifact and local workflow APIs were already marked experimental, with shapes permitted to change in minor releases. This release includes changes that can require updates even though existing single-body calls and workflow entry points remain available:-
SdkWriteArtifactInputis now a body-or-members union. An interface cannot extend that union. For existing body-specific extensions, narrow the input: - Workflow statuses and events include new cases, including terminal refusal. Update exhaustive switches deliberately. Do not treat refusal as cancellation, success or a resumable state.
- Workflow starts capture their durable JSON inputs synchronously. Returned and reopened inputs agree: dates become strings, hidden fields are omitted and sparse arrays/function fields follow JSON normalization. JSON hooks remain supported. Typed action inputs still validate their declared schema; this is not permission to coerce invalid action fields.
-
The
Wikiinterface has additional required members. Hand-written full implementations or test doubles may need to implement them. For a consumer that needs only a few methods, type its dependency and its test double asPick<Wiki, "status" | "getPage">(using the methods it actually consumes), rather than casting an incomplete object to the full interface.
Safety and failure behavior
Pending mutation journals are recovered before further writes. Archive overwrite, selected filename/record-ID mismatch and detected confined-path drift are refused. Legacy relation compaction refuses operation-bound history rather than discarding recovery provenance. These refusals may expose unsafe assumptions in callers; they are not reasons to bypass compiler checks. A write error after rename does not establish that no write happened. Observe and reconcile uncertain outcomes before retrying. Retained artifacts are verified against current bytes, not merely their recorded digests. Composition with a duplicate core module instance is rejected before I/O, including at standard package import or CLI load, not only when starting a workflow. If startup fails after changing dependencies, check that the standard package and local engine resolve the same exact core installation; do not suppress the identity check.Adoption checklist
- Retain the standard package unless you deliberately want an engine-free SDK.
- Install matching release packages; avoid mixing versions or duplicate core copies.
- Type-check your application’s artifact extensions and exhaustive workflow switches.
- Reopen an existing project and exercise your actual CLI or SDK integration.
- Keep operator approval separate from embedder preparation authority.