Skip to content

Version compatibility

Cratis spans .NET packages, TypeScript packages, Docker images, storage engines, React components, Storybook, and documentation tooling. This page gives the current compatibility baseline used by the documentation site. For exact released package versions, use the package manager and repository release pages linked from What’s new.

AreaBaseline
.NET local development.NET 10 is the current development target in Chronicle, Arc, Fundamentals, and CLI source.
.NET package targetingArc and Fundamentals package across net8.0, net9.0, and net10.0 in release configuration. Chronicle packaging also carries net8.0, net9.0, and net10.0 where configured.
CLIThe cratis CLI targets net10.0 in the current source tree.
NodeArc, Components, and Fundamentals JavaScript workspaces declare node >=23.0.0.
Package managerThe JavaScript workspaces use Yarn 4.5.3.
ReactArc React declares React 18 or 19 peer compatibility. Components is currently built and documented around the React 19 workspace.
TypeScriptCurrent JavaScript workspaces use TypeScript 6.
Chronicle storageMongoDB, PostgreSQL, Microsoft SQL Server, and SQLite are documented storage choices.
Arc persistenceMongoDB and Entity Framework Core integrations are documented.
Docs siteAstro Starlight, generated product content, Storybook builds, API reference builds, and /llms.txt exports are part of the documentation site.
ProductCommon dependency relationship
ChronicleUses Fundamentals and Arc packages internally, exposes .NET clients and gRPC/protobuf contracts, and can be inspected through CLI and Workbench.
ArcUses Fundamentals and can integrate with Chronicle, MongoDB, Entity Framework Core, ASP.NET Core, OpenAPI, Swagger, and generated TypeScript proxies.
ComponentsDepends on Arc-generated frontend contracts and React; wraps PrimeReact-oriented UI patterns.
CLITalks to Chronicle and produces AI command catalogs through cratis init.
DocumentationAggregates product Documentation/ folders and builds Storybook/API reference artifacts into the site.
  1. Check the package versions you plan to install.
  2. Check the matching release notes in What’s new.
  3. Check the product guide for runtime-specific setup.
  4. Pin container images and package versions in production.
  5. Ask in Community and help if your runtime combination is not listed.