v0.19.0-dev.7

Fixed

• Fix DhtOps helper functions getChainOpType, getChainOpAction, getChainOpEntry and getChainOpSignature to adhere to the new types

Changed

• Updated types to the new enum serialization convention. The following types are affected:

  • SignalType
  • CellInfo
  • InstallAppRequest
  • RoleSettings
  • DnaSource
  • RegisterDnaRequest
  • CoordinatorSource
  • AppBundleSource
  • AppStatusFilter
  • CloneCellId
  • GrantedFunctions
  • CapAccess
  • DnaStorageBlob

  Enum variants are now consistently snake_case and typically distinguished by a type attribute, unless for enums with exclusively unit-like variants.

  Example 1:

  // OLD
  export type AppBundleSource =
    | { bundle: AppBundle }
    | { path: string };
  
  // NEW
  export type AppBundleSource =
  | {
      type: "path";
      value: string;
    }
  | {
      type: "bundle";
      value: AppBundle;
    };
  

  Example 2 (unit-like variants only):

  // OLD
  export enum AppStatusFilter {
    Enabled = "Enabled",
    Disabled = "Disabled",
    Running = "Running",
    Stopped = "Stopped",
    Paused = "Paused",
  }
  
  // NEW
  export enum AppStatusFilter {
    Enabled = "enabled",
    Disabled = "disabled",
    Running = "running",
    Stopped = "stopped",
    Paused = "paused",
  }
  

v0.18.0

Fixed

• Fixed ChainIntegrityWarrantType

v0.18.0-rc.2

Fixed

• Fix DhtOps helper functions getChainOpType, getChainOpAction, getChainOpEntry and getChainOpSignature to adhere to the new types

v0.18.0-rc.1

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.
• Compatible with Holochain 0.4.0-rc.2

v0.19.0-dev.6

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

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

Fixed

• Bring back optional cap_secret to zome call parameters.

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.

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.

v0.18.0-rc.0

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