Bumped dependencies and rust toolchain

holochain · Feb 23, 2022 · 23da0ae · 23da0ae
1 parent 90da18d
commit 23da0ae
Show file tree

Hide file tree

Showing 10 changed files with 169 additions and 247 deletions.
diff --git a/.github/workflows/release.yaml b/.github/workflows/release.yaml
@@ -24,7 +24,7 @@ jobs:
         uses: actions-rs/toolchain@v1
         with:
           override: true
-          toolchain: 1.55
+          toolchain: 1.58
       - name: install app dependencies and info
         run: npm install && npm run tauri info
       - name: download caddy (Windows only)

diff --git a/.github/workflows/test.yaml b/.github/workflows/test.yaml
@@ -20,7 +20,7 @@ jobs:
         uses: actions-rs/toolchain@v1
         with:
           override: true
-          toolchain: 1.55
+          toolchain: 1.58
       - name: install webkit2gtk (ubuntu only)
         run: |
           sudo apt-get update

diff --git a/README.md b/README.md
@@ -25,8 +25,8 @@ If you already have a `.webhapp`
 
 Requirements:
 
-- On the zome side, target `hdk v0.0.116`.
-- On the UI side, target `@holochain/conductor-api v0.2.4` (v0.2.0 is not going to work).
+- On the zome side, target `hdk v0.0.122`.
+- On the UI side, target `@holochain/client v0.3.2` (v0.2.x is not going to work).
 
 When your UI is served from the launcher and `AppWebsocket.connect()` or `AdminWebsocket.connect()` are called, the call will be redirected to the actual port in which Holochain is running its interfaces. Also, when the `appWebsocket.appInfo({ installed_app_info: <APP_ID> })` is called, the `APP_ID` parameter is going to be replaced with the actual application ID that is installed in the Launcher.