Skip to content

[5.5.7] - 2019-05-13


  • Changed the gem name from ldclient-rb to launchdarkly-server-sdk.

There are no other changes in this release. Substituting ldclient-rb version 5.5.6 with launchdarkly-server-sdk version 5.5.7 will not affect functionality.

Assets 2

@LaunchDarklyCI LaunchDarklyCI released this May 10, 2019 · 3 commits to master since this release

[5.5.6] - 2019-05-08


  • CI tests now include Ruby 2.6.x.
  • Running the SDK unit tests is now simpler, as the database integrations can be skipped. See

Note on future releases

The LaunchDarkly SDK repositories are being renamed for consistency. This repository is now ruby-server-sdk rather than ruby-client.

The gem name will also change. In the 5.5.6 release, it is still ldclient-rb; in all future releases, it will be launchdarkly-server-sdk. No further updates to the ldclient-rb gem will be published after this release.

Assets 2

@LaunchDarklyCI LaunchDarklyCI released this Mar 29, 2019 · 6 commits to master since this release

[5.5.5] - 2019-03-28


  • Setting user attributes to non-string values when a string was expected would cause analytics events not to be processed. Also, in the case of the secondary attribute, this could cause evaluations to fail for a flag with a percentage rollout. The SDK will now convert attribute values to strings as needed. (#131)
Assets 2

@LaunchDarklyCI LaunchDarklyCI released this Mar 21, 2019 · 9 commits to master since this release

[5.5.4] - 2019-03-29


  • Fixed a missing require that could sometimes cause a NameError to be thrown when starting the client, depending on what other gems were installed. This bug was introduced in version 5.5.3. (#129)
  • When an analytics event was generated for a feature flag because it is a prerequisite for another flag that was evaluated, the user data was being omitted from the event. (#128)
  • If track or identify is called without a user, the SDK now logs a warning, and does not send an analytics event to LaunchDarkly (since it would not be processed without a user).
  • Added a link from the SDK readme to the guide regarding the client initialization.
Assets 2

@eli-darkly eli-darkly released this Feb 14, 2019 · 13 commits to master since this release

[5.5.3] - 2019-02-13


  • The SDK previously used the faraday and net-http-persistent gems for all HTTP requests other than streaming connections. Since faraday lacks a stable version and has a known issue with character encoding, and net-http-persistent is no longer maintained, these have both been removed. This should not affect any SDK functionality.


  • The SDK was not usable in Windows because of net-http-persistent. That gem has been removed.
  • When running in Windows, the event-processing thread threw a RangeError due to a difference in the Windows implementation of concurrent-ruby. This has been fixed.
  • Windows incompatibilities were undetected before because we were not running a Windows CI job. We are now testing on Windows with Ruby 2.5.
Assets 2

@LaunchDarklyCI LaunchDarklyCI released this Feb 14, 2019 · 16 commits to master since this release

[5.5.2] - 2019-01-18


  • Like 5.5.1, this release contains only documentation fixes. Implementation classes that are not part of the supported API are now hidden from the generated documentation.
Assets 2

@LaunchDarklyCI LaunchDarklyCI released this Feb 14, 2019 · 19 commits to master since this release

[5.5.1] - 2019-01-17


  • Fixed several documentation comments that had the wrong parameter names. There are no other changes in this release; it's only to correct the documentation.
Assets 2

@LaunchDarklyCI LaunchDarklyCI released this Jan 18, 2019 · 22 commits to master since this release

[5.5.0] - 2019-01-17


  • It is now possible to use Consul or DynamoDB as a persistent feature store, similar to the existing Redis integration. See the LaunchDarkly::Integrations::Consul and LaunchDarkly::Integrations::DynamoDB modules, and the reference guide Using a persistent feature store.
  • There is now a LaunchDarkly::Integrations::Redis module, which is the preferred method for creating a Redis feature store.
  • All of the database feature stores now support local caching not only for individual feature flag queries, but also for all_flags_state.
  • The Config property data_source is the new name for update_processor and update_processor_factory.


  • The implementation of the SSE protocol for streaming has been moved into a separate gem, ld-eventsource. This has no effect on streaming functionality.


  • Added or corrected a large number of documentation comments. All API classes and methods are now documented, and internal implementation details have been hidden from the documentation. You can view the latest documentation on RubyDoc.
  • Fixed a problem in the Redis feature store that would only happen under unlikely circumstances: trying to evaluate a flag when the LaunchDarkly client had not yet been fully initialized and the store did not yet have data in it, and then trying again when the client was still not ready but the store did have data (presumably put there by another process). Previously, the second attempt would fail.
  • In polling mode, the SDK did not correctly handle non-ASCII Unicode characters in feature flag data. (#90)


  • This implementation class may be changed or moved in the future; use LaunchDarkly::Integrations::Redis::new_feature_store.
  • Config.update_processor and Config.update_processor_factory; use Config.data_source.
Assets 2

@eli-darkly eli-darkly released this Jan 15, 2019 · 25 commits to master since this release

[5.4.3] - 2019-01-11


  • The SDK is now compatible with net-http-persistent 3.x. (Thanks, CodingAnarchy!)
Assets 2

@eli-darkly eli-darkly released this Jan 6, 2019 · 27 commits to master since this release

[5.4.2] - 2019-01-04


  • Fixed overly specific dependency versions of concurrent-ruby and semantic. (#115)
  • Removed obsolete dependencies on hashdiff and thread_safe.
Assets 2
You can’t perform that action at this time.