Ably's changelog
Ably's changelog
www.ably.com

Ruby Client Library SDK release v1.2.1

 

Client Library SDK Fix

  

Full Changelog

Fixed bugs:

  • Update Ruby version (and Gemfile.lock dependencies) #253
  • Error not emitted when failing to connect to an endpoint indefinitely #233
  • Connection errors when there should be warnings #198
  • Implement presence re-entry requirement change for 1.1 #185

JavaScript Client Library SDK release v1.2.22

 

Client Library SDK Fix

  
  • Fix bug in RealtimeChannel.subscribe promisify when second argument is undefined #984
  • Update deprecated NativeScript application settings import #980

API Reference docs are now more easily discoverable

We are updating our docs site to make you more successful with Ably.

As a first step, we have made it easier for you to find and use our API Reference docs by listing them as a separate section in the table of contents.

We’ve also made some other minor changes as part of this work:

  • The pages previously listed under “Core features” (including the Auth & Security page) can now be found in the “Getting Started” section under “Key concepts”.
  • Some pages that link to additional resources can be found under “Useful Resources”.
  • Finally, the Server-Sent Events (SSE) and MQTT pages can be found under “Products > Protocol Adapters”.

How do I give feedback?

This docs update and further planned changes are based on feedback from customers like you. So if you’d like to share any other requests or feedback, please contact us and help us make Ably better for everyone.

 

Docs

 

Improvement

  

Go Client Library SDK release v1.2.6

 

Client Library SDK Improvement

  

Full Changelog

Fixed bugs:

  • AblyREST.Request() does not work #486
  • Callback not invoked, despite message being received from server #434
  • Undescriptive errors; possible broken fallback functionality #125
  • HTTPPaginatedResult and PaginatedResult are missing some methods #120
  • ID and Client ID is blank on realtime incoming messages. #58
  • Do not persist authorise attributes force & timestamp #54

Closed issues:

  • go Update urls in readme #491
  • Research a new API Design that allows Ably to be mocked in unit tests. #488
  • Once test observability is in place try to turn all tests back on. #479
  • Support Go 1.18 #474
  • Test improvements - Standardise test assertions #456
  • Investigate re-enabling flaky tests. #438
  • Skipped Test: TestPresenceGet_RSP3_RSP3a1 #415
  • Skipped Test: TestPresenceHistory_RSP4_RSP4b3 #414
  • Skipped Test: TestHistory_Direction_RSL2b2 #413
  • Skipped Test: TestRealtimePresence_EnsureChannelIsAttached #412
  • Skipped Test: TestRealtimePresence_Sync250 #411
  • Skipped Test: TestRealtimeConn_BreakConnLoopOnInactiveState #410
  • Skipped Test: TestRealtimeConn_RTN19b #407
  • Skipped Test: TestRealtimeConn_RTN23 #405
  • Skipped Test: TestRealtimeConn_RTN15d_MessageRecovery #404
  • Skipped Test: TestRealtimeConn_RTN12_Connection_Close RTN12d #403
  • Skipped Test: TestRealtime_DontCrashOnCloseWhenEchoOff #400
  • Skipped Test: TestRealtimeChannel_RTL4_Attach RTL4j2 #398
  • Skipped Test: TestAuth_RSA7c #393
  • Document ably/export_test.go #352
  • Rename ClientOption type to something better describing its purpose #348
  • Clean up ably/doc_test.go Example_paginatedResults() #345
  • Update golang.org/x/net dependency (January 2019 > June 2021) #341
  • Flaky test in 1.2 branch: TestRealtimePresence_Sync250 #338
  • Flaky test in 1.2 branch: TestRealtimeConn_RTN19b #333
  • ably-go: add logging to rest & realtime clients #38

Merged pull requests:

JavaScript Client Library SDK release v1.2.21

 

Client Library SDK Fix

  
  • Make Connection.id and Connection.key optional #952
  • Remove support for MozWebSocket #954
  • Fix a bug with promisified EventEmitter.whenState #962
  • Update ably.com/documentation urls #964
  • Remove console.log statements from msgpack encoder #966
  • Fix nativescript bundle #971

Java Client Library SDK release v1.2.12

 

Client Library SDK Fix

  

Fixed bugs:

  • Cannot automatically re-enter channel due to mismatched connectionId #761
  • Ensure that weak SSL/TLS protocols are not used #749

Two-Factor Authentication for your Ably Account

 

New feature

  

Two-factor authentication (2FA) adds a layer of security to your Ably account by requiring more than just a password to log into the Ably dashboard.

Great news: it's now available for general availability with support for Time-based one-time password (TOTP).

How does it work?

Once a user has enabled 2FA, when they log into your Ably account with a password, they can choose an additional verification step.

Please note: 2FA is only relevant for those using passwords to log in, so excludes Google, Twitter, GitHub and SAML-based authentication.

How do I try it?

Navigate to My Settings in your Ably dashboard, click on the Enable two-factor authentication button, and follow the instructions.

How do I give feedback?

We rely on your feedback and feature requests to improve it. You can contact us at any time if you would like to talk about contributing or feature requests.

.NET Client Library SDK release v1.2.8

 

Client Library SDK Improvement

  

Full Changelog

Implemented enhancements:

  • Unity Beta 2 release. Added example chat app (unity/Assets/Ably/Examples/Chat) along with Edit and Play mode unit tests (unity/Assets/Tests).

Merged pull requests:

Ruby Client Library SDK release v1.2.0

 

Client Library SDK Improvement

  

This release updates ably-ruby to be compliant with the 1.2 version of the Ably client library feature specification. There are some minor breaking changes, please see the migration guide for more information.

Closed issues:

  • Add Channel.setOptions method #291
  • Add support for channel params #288
  • Use ATTACH_RESUME flag for unclean attaches #287
  • Add ChannelOptions param to Channels.get #285
  • Update library to adhere to new spec for token renewal (see the spec definition for more info) #268

JavaScript Client Library SDK release v1.2.19

 

Client Library SDK Fix

  
  • Fix error where some promisified REST methods caused call stack errors #943
  • Fix wasClean implementation for reactnative websocket transport #946
  • Ensure that Ably-Agent is always URI encoded #947