Skip to content

Releases: holochain/holochain-client-js

v0.19.0-dev.6

28 Nov 21:41
83108f7
Compare
Choose a tag to compare
v0.19.0-dev.6 Pre-release
Pre-release

Changed

  • Change InstallAppRequest type to adhere to the new format that includes the roles_settings field and removes
    the membrane_proofs field as membrane proofs are now specified as part of the roles_settings.

v0.19.0-dev.5

21 Nov 22:35
Compare
Choose a tag to compare
v0.19.0-dev.5 Pre-release
Pre-release

Changed

  • Simplify zome call parameters. cap_secret, provenance and payload are optional parameters of a CallZomeRequest. If implicit zome call signing is used, which happens when calling a zome with a CallZomeRequest, provenance and cap_secret are automatically set with the authorized signing credentials. It is still possible to call a cell by its role name instead of its cell id. Alternatively to passing in a CallZomeRequest, callZome can be invoked with a signed request CallZomeRequestSigned, where the zome call parameters have already been serialized and signed.

v0.19.0-dev.4

21 Nov 18:59
Compare
Choose a tag to compare
v0.19.0-dev.4 Pre-release
Pre-release

Fixed

  • Bring back optional cap_secret to zome call parameters.

v0.19.0-dev.3

21 Nov 02:57
Compare
Choose a tag to compare
v0.19.0-dev.3 Pre-release
Pre-release

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.

v0.19.0-dev.2

13 Nov 01:42
Compare
Choose a tag to compare
v0.19.0-dev.2 Pre-release
Pre-release

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.

v0.18.0-rc.0

29 Oct 23:28
Compare
Choose a tag to compare
v0.18.0-rc.0 Pre-release
Pre-release

Added

  • Bring back a websocket reconnection automation for Admin and App websockets. When either of them is closed and a new request made, it will attempt to reconnect using the same app authentication token that was used to initially authenticate the websocket. A specific InvalidTokenError is returned if that fails.

Changed

  • Update to Holochain 0.4.0-rc.0

v0.19.0-dev.1

28 Oct 19:50
Compare
Choose a tag to compare
v0.19.0-dev.1 Pre-release
Pre-release

Added

  • Bring back a websocket reconnection automation for Admin and App websockets. When either of them is closed and a new request made, it will attempt to reconnect using the same app authentication token that was used to initially authenticate the websocket. A specific InvalidTokenError is returned if that fails.

v0.19.0-dev.0

10 Oct 02:08
Compare
Choose a tag to compare
v0.19.0-dev.0 Pre-release
Pre-release

Changed

  • Update to Holochain 0.5.0-dev.0

v0.18.0-dev.13

30 Sep 23:38
Compare
Choose a tag to compare
v0.18.0-dev.13 Pre-release
Pre-release

Fixed

  • Type RevokeAgentKeyResponse, which returns an array of tuples with cell id and error message for all cells that key revocation failed for.

v0.18.0-dev.12

30 Sep 23:25
Compare
Choose a tag to compare
v0.18.0-dev.12 Pre-release
Pre-release

Added

  • Admin API call RevokeAgentKey.