Tooling Compatibility Tables

These tables help you keep the dependencies of all your hApp’s components up to date and — most importantly — in sync with each other.

• Holochain 0.5 compatibility table (current recommended release)

General guidance

We use SemVer to indicate component version compatibility. As a general rule:

• We recommend using the scaffolding tool to create an app, because it’ll ensure that all version numbers are in sync.
• To upgrade your hApp, follow the general instructions for your release, and check the corresponding table above for exact version numbers.
• When we talk about Holochain versions in general, we’re referring to the holochain core library. Its most significant number is the reference point for the rest of the components’ compatibility, and the versions of the conductor binary, hc CLI, and hcterm CLI follow it.
• Compatible hdk library versions share a most significant number with the core library.
• The hdi library’s most significant number is one higher than the core library (e.g., for holochain 0.5, compatible hdi versions are 0.6.x).
• From Holochain 0.5 onwards, the most significant number of the scaffolding, hc-spin, playground, and hc-launch CLI tools is the same as that of the core library, but multiplied by 100. For instance, for Holochain 0.5, use version 0.500.x of these tools.
• The lair keystore, Kitsune2 bootstrap server, Rust and JavaScript clients, Tryorama library, and kangaroo-electron app template repo have their own version number sequences, but almost always advance by one for every new Holochain release series. For example, if JavaScript client 0.18.x is compatible with Holochain 0.4, then JavaScript client 0.19.x will be compatible with Holochain 0.5.

To check the versions you’re currently using in a scaffolded project, use the hn-introspect command from within your project’s Nix dev shell.