@xmtp/[email protected]

@xmtp/[email protected] (2022-12-09)

Bug Fixes

• rename and refactor (564ec77)
• rename to v2 cache (870710f)
• use callback for loading (568ae2d)

Features

• add v2 conversation cache (ecbed6b)

@xmtp/[email protected]

@xmtp/[email protected] (2022-12-09)

Bug Fixes

• bad import (9e632c7)
• break up the utils to multiple files (1532917)

@xmtp/[email protected]

@xmtp/[email protected] (2022-12-05)

Features

• add method to determine msg origin (af0b801)

@xmtp/[email protected]

@xmtp/[email protected] (2022-12-05)

Bug Fixes

• have correct version in package (b879465)

@xmtp/[email protected]

@xmtp/[email protected] (2022-12-01)

Features

• remove stale reference in CONTRIBUTING.md (fdf5886)

@xmtp/[email protected]

@xmtp/[email protected] (2022-11-22)

Bug Fixes

• update for proto@@xmtp/[email protected] (#228) (a0c3a10)

@xmtp/[email protected]

@xmtp/[email protected] (2022-11-11)

Bug Fixes

• maintain pre-existing legacy conversation (#222) (2f8db1a)

@xmtp/[email protected]

@xmtp/[email protected] (2022-11-08)

Bug Fixes

• bump actions/setup-node to v3 (#216) (2868899)

@xmtp/[email protected]

@xmtp/[email protected] (2022-11-08)

This release furthers the rollout of the V2 of the protocol. It switches the default published contact bundle to V2. Clients that are initiating a conversation with a peer that advertises a V2 contact will use V2 conversation flow automatically (prior to this release only conversations with non empty conversation ID would use the V2 flow). This will gradually increase the ratio of V2 network traffic as more and more clients adopt @xmtp/[email protected].

Note that V1 contacts are still being published as well to prevent situations where V1 clients cannot talk to V2 clients if they never published a V1 contact.

@xmtp/[email protected]

@xmtp/[email protected] (2022-11-02)

Bug Fixes

• log info instead of warn on resubscription (9099f93)