From 3ed0a7502dfec5e57a3631c06546312015f31e3b Mon Sep 17 00:00:00 2001 From: ThetaSinner Date: Mon, 31 Aug 2026 15:31:24 +0100 Subject: [PATCH] docs: add missing details to the 0.6 to 0.7 upgrade guide Three additions from #648: - Correct the hc-spin "from" version. 0.601.3 wasn't the last 0.6-line release; 0.603.0 was. - Note the holochain_serialized_bytes pin. The 0.0.56 to 0.0.57 bump landed in hdi 0.7.1, partway through the 0.6 line, so it only affects apps that stayed on an early 0.6 release and pin the crate explicitly. Cargo can't resolve it on its own because 0.0.x releases are mutually incompatible and hdi requires exactly =0.0.57. - Cover the Tryorama package rename. The 0.7-compatible release is published as @holochain-open-dev/tryorama 0.20.0; @holochain/tryorama stops at 0.19.2. --- .../upgrade/upgrade-holochain-0.7.md | 29 +++++++++++++++++-- 1 file changed, 27 insertions(+), 2 deletions(-) diff --git a/src/pages/resources/upgrade/upgrade-holochain-0.7.md b/src/pages/resources/upgrade/upgrade-holochain-0.7.md index 2a6d0b73a..a3fd1e9f7 100644 --- a/src/pages/resources/upgrade/upgrade-holochain-0.7.md +++ b/src/pages/resources/upgrade/upgrade-holochain-0.7.md @@ -67,7 +67,7 @@ To upgrade your hApp written for Holochain 0.6, follow these steps: ```diff:json { "devDependencies": { - - "@holochain/hc-spin": "^0.601.3", + - "@holochain/hc-spin": "^0.603.0", + "@holochain/hc-spin": "^0.700.0", "concurrently": "^6.5.1", "get-port-cli": "^3.0.0" @@ -113,6 +113,16 @@ Update the `hdk` and `hdi` version strings in the project's root `Cargo.toml` fi The latest version numbers of these libraries can be found on `crates.io`: [`hdi`](https://crates.io/crates/hdi), [`hdk`](https://crates.io/crates/hdk). +If your workspace pins `holochain_serialized_bytes` to an explicit version, change it to `0.0.57`: + +```diff:toml + [workspace.dependencies] +-holochain_serialized_bytes = "0.0.56" ++holochain_serialized_bytes = "0.0.57" +``` + +This one is easy to miss, because it isn't really a 0.7 change: the bump happened in `hdi` 0.7.1, partway through the 0.6 line, so you'll only still be on `0.0.56` if you stayed on an early 0.6 release. It also won't fix itself. Cargo treats `0.0.x` releases as mutually incompatible, and `hdi` depends on `holochain_serialized_bytes` with an exact `=0.0.57` requirement, so a `0.0.56` pin is a version conflict rather than something `cargo update` can resolve. If you'd rather not track this crate's version yourself, `holochain_serialized_bytes = "*"` follows whatever `hdi` pins. + If your coordinator zomes have a `holochain` dev-dependency for Sweettest tests, its feature list needs three changes: the `sqlite-encrypted` feature has been replaced by `encryption`, `wasmer_sys` has been renamed to `wasmer-sys-cranelift`, and `transport-iroh` no longer exists because iroh is now compiled in unconditionally. @@ -164,7 +174,22 @@ Update the client library in `ui/package.json`: }, ``` -If you still use Tryorama for your tests rather than Sweettest, it's community-managed at [`holochain-open-dev/tryorama`](https://github.com/holochain-open-dev/tryorama). All the [client library changes](#javascript-client-changes) below apply to Tryorama tests too. +If you still use Tryorama for your tests rather than Sweettest, it's community-managed at [`holochain-open-dev/tryorama`](https://github.com/holochain-open-dev/tryorama). Its 0.7-compatible release is published under a new NPM package name, so edit your project's `tests/package.json` file to swap the old package for the new one: + + + +```diff:json + "dependencies": { + // some dependencies +- "@holochain/client": "^0.20.5", +- "@holochain/tryorama": "^0.19.2", ++ "@holochain/client": "^0.21.0", ++ "@holochain-open-dev/tryorama": "^0.20.0", + // more dependencies + }, +``` + +You'll also need to update the import specifier in any test file that imports from `@holochain/tryorama`. All the [client library changes](#javascript-client-changes) below apply to Tryorama tests too. Then in your project's root folder, run your package manager's install command to update the lockfile and install the new package versions: