Holochain Upgrade 0.4 → 0.5

For existing hApps that are currently using Holochain 0.4, here’s the guide to get you upgraded to 0.5.

The biggest change in Holochain 0.5 is kitsune2, a new wire protocol implementation promises better gossip performance. Kitsune2 is incompatible with the wire protocols used in Holochain 0.4 and prior, so conductors running 0.5 won’t be able to communicate with conductors running earlier releases.

Quick instructions

To upgrade your hApp written for Holochain 0.5, follow these steps:

  1. Update your flake.nix to use the 0.5 version of Holochain. This involves changing the version numbers of two packages.

    Your `flake.nix` might look different

    Depending on the age of your project, you might need to make extra changes to make it look like the one below. If you’re upgrading a project that was created for Holochain 0.3 or earlier, use the ‘Copy’ button on the diff below and replace the contents of your flake.nix with the copied text.

     {
   description = "Flake for Holochain app development";
   inputs = {
-    holonix.url = "github:holochain/holonix?ref=main-0.4";
+    holonix.url = "github:holochain/holonix?ref=main-0.5";
     nixpkgs.follows = "holonix/nixpkgs";
     flake-parts.follows = "holonix/flake-parts";
-    playground.url = "github:darksoil-studio/holochain-playground?ref=main-0.4";
   };
   outputs = inputs@{ flake-parts, ... }: flake-parts.lib.mkFlake { inherit inputs; } {
     systems = builtins.attrNames inputs.holonix.devShells;
     perSystem = { inputs', pkgs, ... }: {
       formatter = pkgs.nixpkgs-fmt;
       devShells.default = pkgs.mkShell {
         inputsFrom = [ inputs'.holonix.devShells.default ];
         packages = (with pkgs; [
           nodejs_20
           binaryen
-          inputs'.playground.packages.hc-playground
         ]);
         shellHook = ''
           export PS1='\[\033[1;34m\][holonix:\w]\$\[\033[0m\] '
         '';
       };
     };
   };
 }

    Don’t worry if you don’t have the hc-playground lines in your flake. This was added after the first release of 0.4, so you can safely ignore it if you don’t have it. It is now included in Holonix by default, so it will be available when you next open a Nix shell.

    This will take effect later when you enter a new Nix shell. It’s important to update your Nix flake lockfile at this point, to ensure you benefit from the cache we provide:

    nix flake update && git add flake.* && nix develop

  2. Update your root package.json file with the new package versions, along with a change to accommodate Playground being bundled with Holonix and the local network services being supplied by a new binary:

     {
     "name": "movies-dev",
     "private": true,
     "workspaces": [
         "ui",
         "tests"
     ],
     "scripts": {
         "start": "AGENTS=${AGENTS:-2} BOOTSTRAP_PORT=$(get-port) SIGNAL_PORT=$(get-port) npm run network",
         "network": "hc sandbox clean && npm run build:happ && UI_PORT=$(get-port) concurrently \"npm run start --workspace ui\" \"npm run launch:happ\" \"hc playground\"",
         "test": "npm run build:zomes && hc app pack workdir --recursive && npm run test --workspace tests",
         "launch:happ": "hc-spin -n $AGENTS --ui-port $UI_PORT workdir/movies5.happ",
         "start:tauri": "AGENTS=${AGENTS:-2} BOOTSTRAP_PORT=$(get-port) npm run network:tauri",
-        "network:tauri": "hc sandbox clean && npm run build:happ && UI_PORT=$(get-port) concurrently \"npm run start --workspace ui\" \"npm run launch:tauri\" \"holochain-playground\"",
+        "network:tauri": "hc sandbox clean && npm run build:happ && UI_PORT=$(get-port) concurrently \"npm run start --workspace ui\" \"npm run launch:tauri\" \"hc playground\"",
-        "launch:tauri": "concurrently \"hc run-local-services --bootstrap-port $BOOTSTRAP_PORT --signal-port $SIGNAL_PORT\" \"echo pass | RUST_LOG=warn hc launch --piped -n $AGENTS workdir/movies5.happ --ui-port $UI_PORT network --bootstrap http://127.0.0.1:\"$BOOTSTRAP_PORT\" webrtc ws://127.0.0.1:\"$SIGNAL_PORT\"\"",
+        "launch:tauri": "concurrently \"kitsune2-bootstrap-srv --listen \"127.0.0.1:$BOOTSTRAP_PORT\"\" \"echo pass | RUST_LOG=warn hc launch --piped -n $AGENTS workdir/movies5.happ --ui-port $UI_PORT network --bootstrap http://127.0.0.1:\"$BOOTSTRAP_PORT\" webrtc ws://127.0.0.1:\"$BOOTSTRAP_PORT\"\"",
         "package": "npm run build:happ && npm run package --workspace ui && hc web-app pack workdir --recursive",
         "build:happ": "npm run build:zomes && hc app pack workdir --recursive",
         "build:zomes": "cargo build --release --target wasm32-unknown-unknown"
     },
     "devDependencies": {
-        "@holochain-playground/cli": "^0.300.0-rc.0",
-        "@holochain/hc-spin": "^0.400.1",
+        "@holochain/hc-spin": "^0.500.1",
         "concurrently": "^6.5.1",
         "get-port-cli": "^3.0.0"
     },
     "engines": {
         "node": ">=16.0.0"
     },
     "hcScaffold": {
         "template": "svelte" // This might be different for your app
     }
 }

    {
    "name": "movies-dev",
    "private": true,
    "workspaces": [
        "ui",
        "tests"
    ],
    "scripts": {
        "start": "AGENTS=${AGENTS:-2} BOOTSTRAP_PORT=$(get-port) SIGNAL_PORT=$(get-port) npm run network",
        "network": "hc sandbox clean && npm run build:happ && UI_PORT=$(get-port) concurrently \"npm run start --workspace ui\" \"npm run launch:happ\" \"hc playground\"",
        "test": "npm run build:zomes && hc app pack workdir --recursive && npm run test --workspace tests",
        "launch:happ": "hc-spin -n $AGENTS --ui-port $UI_PORT workdir/movies5.happ",
        "start:tauri": "AGENTS=${AGENTS:-2} BOOTSTRAP_PORT=$(get-port) npm run network:tauri",
        "network:tauri": "hc sandbox clean && npm run build:happ && UI_PORT=$(get-port) concurrently \"npm run start --workspace ui\" \"npm run launch:tauri\" \"hc playground\"",
        "launch:tauri": "concurrently \"kitsune2-bootstrap-srv --listen \"127.0.0.1:$BOOTSTRAP_PORT\"\" \"echo pass | RUST_LOG=warn hc launch --piped -n $AGENTS workdir/movies5.happ --ui-port $UI_PORT network --bootstrap http://127.0.0.1:\"$BOOTSTRAP_PORT\" webrtc ws://127.0.0.1:\"$BOOTSTRAP_PORT\"\"",
        "package": "npm run build:happ && npm run package --workspace ui && hc web-app pack workdir --recursive",
        "build:happ": "npm run build:zomes && hc app pack workdir --recursive",
        "build:zomes": "cargo build --release --target wasm32-unknown-unknown"
    },
    "devDependencies": {
        "@holochain/hc-spin": "^0.500.1",
        "concurrently": "^6.5.1",
        "get-port-cli": "^3.0.0"
    },
    "engines": {
        "node": ">=16.0.0"
    },
    "hcScaffold": {
        "template": "svelte" // This might be different for your app
    }
}

  3. Update your project’s package dependencies (see below).

  4. Follow the breaking change update instructions below to get your code working again.

  5. Try running your tests:

    npm test

    and starting the application:

    npm start

  6. Be aware of some changes that won’t break your app but may affect its runtime behavior. Read the guide at the bottom.

  7. For production apps, you’ll need to specify new signal, bootstrap, and ICE URLs.

Update your package dependencies

Rust

Update the hdk and hdi version strings in the project’s root Cargo.toml file:

 [workspace.dependencies]
-hdi = "=0.5.2"
-hdk = "=0.4.2"
+hdi = "=0.6.3" # Pick a later patch version of these libraries if you prefer.
+hdk = "=0.5.3"
+holochain_serialized_bytes = "*"

[workspace.dependencies]
hdi = "=0.6.3" # Pick a later patch version of these libraries if you prefer.
hdk = "=0.5.3"
holochain_serialized_bytes = "*"

And update your zomes’ Cargo.toml files as well:

 [dependencies]
 hdk = { workspace = true }
 serde = { workspace = true }
+holochain_serialized_bytes = { workspace = true }

[dependencies]
hdk = { workspace = true }
serde = { workspace = true }
holochain_serialized_bytes = { workspace = true }

The latest version numbers of these libraries can be found on crates.io: hdi, hdk.

Once you’ve updated your Cargo.toml you need to update your Cargo.lock and check whether your project can still build. To do this in one step you can run:

cargo build

(Optional) Update other Rust dependencies

Running a Cargo build, like suggested above, will update as few dependencies as it can. This is good for stability because it’s just making the changes you asked for. However, sometimes you do need to update other dependencies to resolve build issues.

This section is marked as optional because it’s possible that new dependencies could introduce new issues as well as fixing existing conflicts or problems. To make it possible to roll back this change, it might be a good idea to commit the changes you’ve made so far to source control. Then you can run:

cargo update

This will update your Cargo.lock with the latest versions of all libraries that the constraints in your Cargo.toml files will allow. Now you should try building your project again to see if that has resolved your issue.

JavaScript

If you’ve created your hApp using our scaffolding tool, you should be able to follow these instructions. If you’ve created your own project folder layout, adapt these instructions to fit.

Tryorama tests

Edit your project’s tests/package.json file:

   "dependencies": {
     // some dependencies
-    "@holochain/client": "^0.18.1",
-    "@holochain/tryorama": "^0.17.1",
+    "@holochain/client": "^0.19.1",
+    "@holochain/tryorama": "^0.18.2",
     // more dependencies
   },

  "dependencies": {
    // some dependencies
    "@holochain/client": "^0.19.1",
    "@holochain/tryorama": "^0.18.2",
    // more dependencies
  },

UI

You’ll update the UI package dependencies similarly to the test package. Edit ui/package.json:

   "dependencies": {
-    "@holochain/client": "^0.18.1",
+    "@holochain/client": "^0.19.1",
     // more dependencies
   },

  "dependencies": {
    "@holochain/client": "^0.19.1",
    // more dependencies
  },

Then in your project’s root folder, run your package manager’s update command to update the lockfile and install new package versions for your command-line tools, tests, and UI. Use the command that matches your chosen package manager. For example, if you’re using npm:

npm install

Update your application code

Enums in the conductor APIs are serialized differently

The admin and app APIs have changed their serialization of enum variants with values: the variant name and value are now in type and value fields, and variant names have been normalized to snake_case. For instance, if you subscribe to signals in a JavaScript-based front end, you would change your signal handler like this:

 client.on("signal", (sig: Signal) => {
-    if (SignalType.App in sig) {
-        const signal = sig[SignalType.App];
+    if (sig.type == SignalType.App) {
+        const signal = sig.value;
         // ... Handle the app signal
     }
 });

client.on("signal", (sig: Signal) => {
    if (sig.type == SignalType.App) {
        const signal = sig.value;
        // ... Handle the app signal
    }
});

This change happens in many places; we recommend that you run the TypeScript compiler against your UI and tests and look for errors. In the Holonix dev shell, run:

npx tsc -p ui/tsconfig.json

npx tsc -p tests/tsconfig.json

and look for messages that look similar to error TS2322: Type X is not assignable to type Y.

This won’t catch all errors; you may discover some at runtime. Look for usage of the following types and functions in particular:

HoloHash constructors renamed

HoloHash<T>::from_raw_39 is now called HoloHash<T>::try_from_raw_39, and HoloHash<T>::from_raw_39_panicky is now HoloHash<T>::from_raw_39. Remember to check your code for usage of all the aliases of HoloHash – ActionHash, AgentPubKey, AnyDhtHash, AnyLinkableHash, DnaHash, EntryHash, and ExternalHash.

Because the new name of the function that panics is the same as the old name of the function that returns a Result, you may need to do a search-and-replace in two stages.

AppWebsocket::callZome can no longer accept a null cap secret

The cap_secret field in the request argument of AppWebsocket::callZome can no longer be null — instead it must either be omitted (you don’t need it at all if your UI is hosted by an officially supported Holochain runtime) or explicitly given.

 const results = await client.value.callZome({
     role_name: "my_dna",
     zome_name: "my_zome",
     fn_name: "foo",
     payload: null,
-    cap_secret: null,
 });

const results = await client.value.callZome({
    role_name: "my_dna",
    zome_name: "my_zome",
    fn_name: "foo",
    payload: null,
});

origin_time and quantum_time are removed

With the new kitsune2 wire protocol, origin_time and quantum_time are no longer used. You may find these optional fields anywhere integrity modifiers are used:

AgentInfo::agent_latest_pubkey behind feature flag

When you call agent_info from a coordinator zome, the agent_latest_pubkey field in the return value is now hidden behind the unstable-dpki feature flag and scheduled to be removed in 0.6. Anywhere you use this field, use agent_initial_pubkey instead:

 use hdk::prelude::*;

 fn get_my_agent_id() -> ExternResult<AgentPubKey> {
-    Ok(agent_info()?.agent_latest_pubkey)
+    Ok(agent_info()?.agent_initial_pubkey)
 }

use hdk::prelude::*;
fn get_my_agent_id() -> ExternResult<AgentPubKey> {
    Ok(agent_info()?.agent_initial_pubkey)
}

DNA lineage behind feature flag

Features related to DNA lineage are now hidden behind an unstable-migration feature flag. If you don’t plan to use this, remove the lineage line from your dna.yaml file:

 # ...
-lineage:
-  - "hC0kKUej3Mcu+40AjNGcaID2sQA6uAUcc9hmJV9XIdwUJUE" 
-  - "hCAkhy0q54imKYjEpFdLTncbqAaCEGK3LCE+7HIA0kGIvTw" 
 # ...

# ...
# ...

The GetCompatibleCells endpoint in the admin API is also hidden behind this flag.

If you want to use these features, build a custom Holochain binary with unstable-migration enabled. Note that support for the endpoint has been removed from the JavaScript client.

AppBundleSource::Bundle removed

Note: This information is only relevant if you’re building a runtime or using Tryorama’s Conductor.prototype.installApp method, either directly or through a helper like scenario.addPlayersWithApps. The Bundle option (deprecated in 0.4.2) is now removed from AppBundleSource. If you need to pass bundle bytes to the admin API’s InstallApp endpoint, use AppBundleSource::Bytes (introduced in 0.4.2) and pass the bytes of an entire hApp bundle file instead.

Note that, as a conductor API endpoint, InstallApp is also affected by the enum serialization change:

-const playerConfig = { appBundleSource: { path: "./workdir/my_app.happ", } };
+const playerConfig: AppWithOptions = { appBundleSource: { type: "path", value: "./workdir/my_app.happ", } };
 const [alice, bob] = await scenario.addPlayersWithApps([playerConfig, playerConfig]);

const playerConfig: AppWithOptions = { appBundleSource: { type: "path", value: "./workdir/my_app.happ", } };
const [alice, bob] = await scenario.addPlayersWithApps([playerConfig, playerConfig]);

scenario.addPlayerWithApp input now more closely matches addPlayersWithApps

The signature of the Scenario.prototype.addPlayerWithApp method now takes an AppWithOptions object in the same way that addPlayersWithApps takes an array of the same object.

-const appBundleSource: AppBundleSource = { path: "./workdir/my_app.happ" };
+const appBundleSource: AppBundleSource = { type: "path", value: "./workdir/my_app.happ", };
 const options: AppOptions = { networkSeed: "special_network_seed", };
+const playerConfig: AppWithOptions = { appBundleSource, options, };
-const alice = scenario.addPlayerWithApp(appBundleSource, options);
+const alice = scenario.addPlayerWithApp(playerConfig);

const appBundleSource: AppBundleSource = { type: "path", value: "./workdir/my_app.happ", };
const options: AppOptions = { networkSeed: "special_network_seed", };
const playerConfig: AppWithOptions = { appBundleSource, options, };
const alice = scenario.addPlayerWithApp(playerConfig);

hc run-local-services replaced with kitsune2-bootstrap-srv

The old bootstrap and signal server have been combined into one binary called kitsune2-bootstrap-srv, which is provided in the Holonix dev environment for any new scaffolded hApps. To update an existing hApp, edit its flake.nix file to include the binary and optionally update its package.json file to use it if you use the Tauri-based launcher. Locally running hApp instances using hc-spin and hc-launch will now use the new binary.

disableCloneCell, enableCloneCell, and deleteCloneCell signatures changed

The object that you pass to the JS client’s AppWebsocket.prototype.disableCloneCell, AppWebsocket.prototype.enableCloneCell, and AdminWebsocket.prototype.deleteCloneCell methods has changed; now you need to explicitly specify whether the identifier is a clone ID or DNA hash using the new enum serialization format.

 let cellClonedByRoleName = client.createCloneCell({
-    clone_cell_id: "chat.1"
+    clone_cell_id: {
+        type: "clone_id",
+        value: "chat.1"
+   }
 });
 let dnaHash = decodeHashFromBase64("hC0kKUej3Mcu+40AjNGcaID2sQA6uAUcc9hmJV9XIdwUJUE"); 
 let cellClonedByDnaHash = client.createCloneCell({
-    clone_cell_id: dnaHash
+    clone_cell_id: {
+        type: "dna_hash",
+        value: dnaHash
+    }
 });

let cellClonedByRoleName = client.createCloneCell({
    clone_cell_id: {
        type: "clone_id",
        value: "chat.1"
   }
});
let dnaHash = decodeHashFromBase64("hC0kKUej3Mcu+40AjNGcaID2sQA6uAUcc9hmJV9XIdwUJUE"); 
let cellClonedByDnaHash = client.createCloneCell({
    clone_cell_id: {
        type: "dna_hash",
        value: dnaHash
    }
});

Timestamps moved to holochain_timestamp

The Timestamp type used all over the HDK and in scaffolded entry types has been moved to a new crate called holochain_timestamp. This type has historically been made available transitively through hdi::prelude and hdk::prelude, so you shouldn’t need to make any code changes unless you reference the kitsune_p2p_timestamp crate explicitly in any of your Cargo.toml files or code:

 # ...
 [dependencies]
-kitsune_p2p_timestamp = "0.4.2"
+holochain_timestamp = "0.5.3"

# ...
[dependencies]
holochain_timestamp = "0.5.3"
-use kitsune_p2p_timestamp::Timestamp;
+use holochain_timestamp::Timestamp;

 fn get_time() -> ExternResult<Timestamp> {
     sys_time()
 }

use holochain_timestamp::Timestamp;
fn get_time() -> ExternResult<Timestamp> {
    sys_time()
}

App API’s NetworkInfo removed

The NetworkInfo endpoint of the app API has been removed, which means the AppWebsocket.networkInfo method has also been removed. You can get some network info from the DumpNetworkMetrics and DumpNetworkStats endpoints, which are now exposed on the app API.

Networking section of conductor config changed

Note: This only applies if you’re using persistent conductor configs. The network section of conductor-config.yaml files has changed. We recommend that you generate a new conductor config using hc sandbox, then compare it against your existing conductor config to see what changes need to be made. You can find available config keys in the NetworkConfig documentation.

Admin API’s AgentInfo return value changed

Note: This is an advanced feature that you’ll only encounter if you’re building a custom runtime that tries to get diagnostic data. The return value of the AgentInfo endpoint in the admin API has changed. Currently it outputs a vector of JSON-serialized kitsune2_api::AgentInfoSigned values.

Production apps: new network infrastructure servers

With the change to Kitsune2, the public bootstrap and signal server API has changed. Holo is not hosting public servers like they are for Holochain 0.4. For testing, we’re offering public servers you can use. We request and recommend that you maintain your own bootstrap and signal servers for production hApps, as the test servers are rate-limited and have no uptime guarantees. You can find the server binary on crates.io or adapt this example Dockerfile (see this example for TLS configuration).

If you’re bundling your hApp with Kangaroo, you’ll need to add these servers to your kangaroo.config.ts file. The following example shows URLs for the dev test servers and public STUN/ICE servers from Google and Cloudflare, along with new hashes and version numbers for the bundled binaries.

 import { defineConfig } from './src/main/defineConfig';

 export default defineConfig({
   appId: 'org.holochain.kangaroo-electron',
   productName: 'Holochain Kangaroo Electron',
   version: '0.1.0',
   macOSCodeSigning: false,
   windowsEVCodeSigning: false,
   fallbackToIndexHtml: true,
   autoUpdates: true,
   systray: true,
   passwordMode: 'password-optional',
+  // For production hApps, swap the following URLs for your own self-hosted
+  // URLs.
+  bootstrapUrl: 'https://dev-test-bootstrap2.holochain.org/',
+  signalUrl: 'wss://dev-test-bootstrap2.holochain.org/',
+  // You may want to replace these free public STUN server URLs with ones
+  // from your preferred WebRTC provider.
+  iceUrls: ['stun:stun.l.google.com:19302','stun:stun.cloudflare.com:3478'],
     bins: {
     holochain: {
-      version: '0.4.1',
+      version: '0.5.3',
       sha256: {
         'x86_64-unknown-linux-gnu':
-          'ee713408a31d2e17826b18e2eaea0b3e200b42aa0cc8e3562c899b0b5ebcaa0c',
+          '1165646324ad6ebd60fe8063a91ec4981dd1d7da64375603560fcc6b7ef511f7',
         'x86_64-pc-windows-msvc.exe':
-          '9aa248f6e500915085ebf3fd093541cbbdad59a994e7f904260cb4ad788bd1e3',
+          '143791e1c59dd718c5b60face20792a85b752ac3bba0e58b57469690c4be6a19',
-        'x86_64-apple-darwin': '0ce19dfde7db6521cd96e2fef924c62d319d204e7f79bc0379674a7a6122c74f',
+        'x86_64-apple-darwin': '540ef02bcfce6c91379e07df03d51afedc73a1f13df74e0cb9da6be58e147878',
-        'aarch64-apple-darwin': '74dc8d8529a50d24e8338ddd2e9913d6fb34414f6588d11243e6ccb29feda029',
+        'aarch64-apple-darwin': 'a42edb4e8580456c95f8c91ab0699d2b5fd1f73a5df0bdb9e4f20a102de0e988',
       },
     },
     lair: {
      sha256: {
        'x86_64-unknown-linux-gnu':
        'x86_64-pc-windows-msvc.exe':
-      version: '0.5.3',
+      version: '0.6.2',
       sha256: {
         'x86_64-unknown-linux-gnu':
-          '96a28b9b37c73ef46d8b5c56b9d799d558fd2fe77b41c577e2bcb37685a46396',
+          '3c9ea3dbfc0853743dad3874856fdcfe391dca1769a6a81fc91b7578c73e92a7',
         'x86_64-pc-windows-msvc.exe':
-          '68b6453a19921072aac04dae52a4e94e725e7482005d2f54f907aec680e078de',
+          '6392ce85e985483d43fa01709bfd518f8f67aed8ddfa5950591b4ed51d226b8e',
-        'x86_64-apple-darwin': 'a53bfb8e501431870b99243cbac24f6103d67f8be094930f174829bb249f34c4',
+        'x86_64-apple-darwin': '746403e5d1655ecf14d95bccaeef11ad1abfc923e428c2f3d87c683edb6fdcdc',
-        'aarch64-apple-darwin': '6b15d977408847ac977c2e060c7aab84a69e6e90c79390098dd40a6b75256e50',
+        'aarch64-apple-darwin': '05c7270749bb1a5cf61b0eb344a7d7a562da34090d5ea81b4c5b6cf040dd32e8',
       },
     },
   },
 });

import { defineConfig } from './src/main/defineConfig';
export default defineConfig({
  appId: 'org.holochain.kangaroo-electron',
  productName: 'Holochain Kangaroo Electron',
  version: '0.1.0',
  macOSCodeSigning: false,
  windowsEVCodeSigning: false,
  fallbackToIndexHtml: true,
  autoUpdates: true,
  systray: true,
  passwordMode: 'password-optional',
  // For production hApps, swap the following URLs for your own self-hosted
  // URLs.
  bootstrapUrl: 'https://dev-test-bootstrap2.holochain.org/',
  signalUrl: 'wss://dev-test-bootstrap2.holochain.org/',
  // You may want to replace these free public STUN server URLs with ones
  // from your preferred WebRTC provider.
  iceUrls: ['stun:stun.l.google.com:19302','stun:stun.cloudflare.com:3478'],
    bins: {
    holochain: {
      version: '0.5.3',
      sha256: {
        'x86_64-unknown-linux-gnu':
          '1165646324ad6ebd60fe8063a91ec4981dd1d7da64375603560fcc6b7ef511f7',
        'x86_64-pc-windows-msvc.exe':
          '143791e1c59dd718c5b60face20792a85b752ac3bba0e58b57469690c4be6a19',
        'x86_64-apple-darwin': '540ef02bcfce6c91379e07df03d51afedc73a1f13df74e0cb9da6be58e147878',
        'aarch64-apple-darwin': 'a42edb4e8580456c95f8c91ab0699d2b5fd1f73a5df0bdb9e4f20a102de0e988',
      },
    },
    lair: {
     sha256: {
       'x86_64-unknown-linux-gnu':
       'x86_64-pc-windows-msvc.exe':
      version: '0.6.2',
      sha256: {
        'x86_64-unknown-linux-gnu':
          '3c9ea3dbfc0853743dad3874856fdcfe391dca1769a6a81fc91b7578c73e92a7',
        'x86_64-pc-windows-msvc.exe':
          '6392ce85e985483d43fa01709bfd518f8f67aed8ddfa5950591b4ed51d226b8e',
        'x86_64-apple-darwin': '746403e5d1655ecf14d95bccaeef11ad1abfc923e428c2f3d87c683edb6fdcdc',
        'aarch64-apple-darwin': '05c7270749bb1a5cf61b0eb344a7d7a562da34090d5ea81b4c5b6cf040dd32e8',
      },
    },
  },
});

Upgrading your Kangaroo-based project

To get your Kangaroo-based hApp working with Holochain 0.5, you’ll also need to compare your project’s code against the code in the kangaroo-electron template repo for Holochain 0.5 (currently at this commit), make changes as needed, and follow the guidance above for updating UI and zome code.

Subtle changes

The following changes don’t break Holochain’s APIs or require updates to your code, but they may require you to reassess whether your hApp will work as expected:

It looks like you are using Internet Explorer. While the basic content is available, this is no longer a supported browser by the manufacturer, and no attention is being given to having IE work well here.