Be notified of new releases
Create your free GitHub account today to subscribe to this repository for new releases and build software alongside 36 million developers.Sign up
[5.5.7] - 2019-05-13
- Changed the gem name from
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.
[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
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.
[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
secondaryattribute, 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)
[5.5.4] - 2019-03-29
- Fixed a missing
requirethat could sometimes cause a
NameErrorto 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)
identifyis 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.
[5.5.3] - 2019-02-13
- The SDK previously used the
net-http-persistentgems for all HTTP requests other than streaming connections. Since
faradaylacks a stable version and has a known issue with character encoding, and
net-http-persistentis 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
RangeErrordue 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.
[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.
[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.
[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::DynamoDBmodules, and the reference guide Using a persistent feature store.
- There is now a
LaunchDarkly::Integrations::Redismodule, 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
data_sourceis the new name for
- 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)
RedisFeatureStore.new. This implementation class may be changed or moved in the future; use
[5.4.2] - 2019-01-04
- Fixed overly specific dependency versions of
- Removed obsolete dependencies on