Releases: ably/ably-js
Releases · ably/ably-js
1.1.9
- Auth: fix tokenParams missing from token requests in the event that no authParams specified
1.1.8
- Auth: if you do multiple concurrent authorize()s, make sure the token from last one wins
- If fallback hosts are enabled and a connection is abruptly disconnected with a 5xx error, retry immediately to a fallback rather than waiting the usual 15s disconnectedRetryTimeout
1.1.7
- Catch common failure mode with poorly-implemented authCallback
- Fix typings of TokenParams.capability
1.1.6
- Improve handling of responso to active traffic management placement constraint error for smooth cluster handover
- Normalise statuscode for 40170-failure to obtain token from client auth callback to 401 per spec
1.1.5
- Only autoremove an expired token if we know the local offset from server time
- Fix tokenParams not being correctly mixed in to authParams in some circumstances
1.1.4
- Support PUSH, PATCH, and DELETE in Rest#request()
- Support arbitrary params for REST publishes
- Fix scope leak issue when using the minified version of the library
Official 1.1 update
This 1.1 release brings many new features from 1.0:
- Transient publishing supported on channels
- Push notifications are now generally available
- Experimental support for batch REST publishing
- Access to the Ably DSX
See the complete release notes at https://blog.ably.io/ablys-client-library-sdks-1-1-release-8165c73c76fd
1.0.23
- Only make a single token request at a time
- Fix crash with react-native on some Android versions when making REST requests
- Tweak fallback host logic for connected realtime clients making REST requests
1.0.21
- Reinstate 'stop clientId forcing token auth' change (#542)
- Prioritise a tokenParam over an authParam of the same name
- Fix behaviour with multiple concurrent pings in-flight
- Use console.warn (if present) when logging at ERROR level
- Implement client-side-enforced maxMessageSize limit and bundling constraints
- Deduce streaming response from lack of content-length header even if no transfer-encoding
1.0.19
- Expose rest#setLog method to change log level or handler at runtime
- Allow jsonp for REST requests even if allowComet is false
- Expose Rest.Message for node, for consistency with Realtime.Message
- Add updateOnAttached channel option to force 'update' event even if
resumed
is true - Stop a clientId from forcing token auth (#542)
h Fix to NPM package creation that was unnecessarily bloating the package size