Releases: ably/ably-js
v2.10.1
v2.10.0
Full Changelog: 2.9.0...2.10.0
What's Changed
- Add
Channels.all
to type declarations #2040 - Add
ClientOptions.endpoint
parameter and deprecate theenvironment
,restHost
andrealtimeHost
client options. See platform customization documentation for guidance on using the newendpoint
parameter #1973
v2.9.0
Full Changelog: 2.8.0...2.9.0
What's Changed
Introducing Ably LiveObjects
With this release, ably-js now supports LiveObjects.
Ably LiveObjects enables effortless realtime synchronization of application state across multiple users and devices at any scale. When a LiveObject is updated, changes are automatically propagated to all subscribed clients in realtime, ensuring that everyone always sees the latest state.
The ably-js implementation for LiveObjects provides a simple, purpose-built API that handles realtime synchronization, persistence, and convergence behind the scenes.
See our official documentation to learn more about LiveObjects and how to start synchronizing your application state using Ably.
- Add support for Ably LiveObjects #2007
v2.8.0
Full Changelog: 2.7.0...2.8.0
What's Changed
v2.7.0
Full Changelog: 2.6.5...2.7.0
What's Changed
- Adds
ANNOTATION_PUBLISH
andANNOTATION_SUBSCRIBE
channel modes #1953 - Adds support for message annotations via
channel.annotations
#1953 - The message action
meta.occupancy
is now renamed tometa
. Similarly,MessageActions.META_OCCUPANCY
is nowMessageActions.META
#1953 - Fixes a bug where
deactivate
would not use device auth, meaning clients would only be able to use it with thepush-admin
capability #2000 - The push
deactivate
method's callback type is now optional when using TypeScript #2000
v2.6.5
v2.6.4
Full Changelog: 2.6.3...2.6.4
What's Changed
- Adds new capabilities to control the upcoming message operations. #1949
- These include:
message-update-any
- the ability to edit a message created by any client on a given channel.message-update-own
- the ability to edit only the messages created by the requesting client on a given channel.message-delete-any
- the ability to delete a message created by any client on a given channel.message-delete-own
- the ability to delete only the messages created by the requesting client on a given channel.
v2.6.3
Full Changelog: 2.6.2...2.6.3
What's Changed
v2.6.2
Full Changelog: 2.6.1...2.6.2
What's Changed
- Message: fix parent-populated version not being propagated to serial by @SimonWoolf in #1945
v2.6.1
Full Changelog: 2.6.0...2.6.1