chore(release): v0.19.0-dev.3

CHANGELOG.md

@@ -7,9 +7,12 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
 ### Added
 ### Fixed
 ### Changed
-- Zome call signing has been changed in Holochain to remove the requirement of imitating Holochain serialization. Signing is now a simplified process of serializing zome call parameters using MessagePack, then computing a SHA2 512-bit hash of the serialized bytes and signing the hash. The zome call payload consists of the serialized bytes and the signature.
 ### Removed
 
+## 2024-11-20: v0.19.0-dev.3
+### Changed
+- Zome call signing has been changed in Holochain to remove the requirement of imitating Holochain serialization. Signing is now a simplified process of serializing zome call parameters using MessagePack, then computing a SHA2 512-bit hash of the serialized bytes and signing the hash. The zome call payload consists of the serialized bytes and the signature.
+
 ## 2024-11-12: v0.19.0-dev.2
 ### Added
 - AppWebsocket calls to interact with countersigning sessions, i.e. `GetCountersigningSessionState` as well as `AbandonCountersigningSession` and `PublishCountersigningSession` when a session could not be resolved automatically. Countersigning is an unstable feature which must explicitly be enabled in Holochain.

docs/client.callzomerequest.md

@@ -8,7 +8,7 @@
 **Signature:**
 
 ```typescript
-export type CallZomeRequest = CallZomeRequestGeneric<unknown>;
+export type CallZomeRequest = CallZomeRequestGeneric<any>;
 ```
 **References:** [CallZomeRequestGeneric](./client.callzomerequestgeneric.md)
 

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@holochain/client",
-  "version": "0.19.0-dev.2",
+  "version": "0.19.0-dev.3",
   "description": "A JavaScript client for the Holochain Conductor API",
   "author": "Holochain Foundation <[email protected]> (https://holochain.org)",
   "license": "CAL-1.0",