Releases & support
Publish trains, compatibility expectations, and what Restormel supports for npm consumers versus fork-or-extend scenarios.
Release train
Graph packages publish from this monorepo when maintainers push a git tag matching graph-v*. Workflow: publish-graph.yml. Changelog entries for the graph stack live in the root CHANGELOG.md under Graph-related
bullets.
npm (canvas): @restormel/graph-core, @restormel/ui-graph-svelte. Reasoning extensions (separate train): @restormel/graph-reasoning-extensions, @restormel/contracts — see Reasoning extensions & contracts.
Context packs & agent memory (same platform-v* workflow, not canvas): @restormel/context-packs, @restormel/state — overview Restormel State (agent memory); reasoning page links both to the
graph-aware LLM story.
Compatibility matrix
CI and tarball smoke cover the repo’s pinned stack. Consumer apps on adjacent minors should work but should run their
own svelte-check and a smoke route after upgrades.
| Layer | Tested / expected |
|---|---|
| Node.js | >=20 (graph-core engines field) |
| TypeScript | moduleResolution: "NodeNext" or bundler resolution that honours package exports; use
published .d.ts as source of truth for component props |
| Svelte | ^5.0.0 peer on ui-graph-svelte — certify your minor (e.g. 5.20.x) in your app |
| Vite | Vite 5.x and 6.x used in this monorepo; match or exceed demo + dashboard toolchain when upgrading |
| SvelteKit | Aligned with apps/restormel-graph-demo and dashboard; ssr.noExternal for both @restormel/ui-graph-svelte and @restormel/graph-core as documented |
| graph-reasoning-extensions | Published on platform-v*; pin alongside @restormel/contracts — independent of graph-v* |
| context-packs, observability, state | Published on platform-v*; @restormel/state depends on context-packs for correlation
typing — see Restormel State |
Extend this matrix with specific SvelteKit / Vite patch lines as you certify them in production consumers.
Support boundary
- Supported for consumers: documented export paths, Contract v0 DTO stability policy, and canvas behaviour consistent with published versions. Integration guidance on restormel.dev is kept aligned with those releases.
- Fork or extend: deep imports, copied
src, vendored forks with divergent DTOs, or embedding reasoning contracts inside the graph packages—out of scope for upstream support.
Docs vs app releases
The restormel.dev narrative (including /graph/docs) deploys with the dashboard app.
npm packages version on graph-v* tags. Treat integration steps as accurate for the site deployment you
are viewing; cross-check semver on npm when pinning.