4.0.0

[4.0.0] - 2018-05-10

Changed:

• To reduce the network bandwidth used for analytics events, feature request events are now sent as counters rather than individual events, and user details are now sent only at intervals rather than in each event. These behaviors can be modified through the LaunchDarkly UI and with the new configuration option inline_users_in_events. For more details, see Analytics Data Stream Reference.

Removed:

• JRuby 1.7 is no longer supported.
• Greatly reduced the number of indirect gem dependencies by removing moneta, which was previously a requirement for the Redis feature store.

3.0.3

[3.0.3] - 2018-03-23

Fixed

• In the Redis feature store, fixed a synchronization problem that could cause a feature flag update to be missed if several of them happened in rapid succession.

3.0.2

[3.0.2] - 2018-03-06

Fixed

• Improved efficiency of logging by not constructing messages that won't be visible at the current log level. (Thanks, julik!)

3.0.1

[3.0.1] - 2018-02-26

Fixed

• Fixed a bug that could prevent very large feature flags from being updated in streaming mode.

3.0.0

[3.0.0] - 2018-02-22

Added

• Support for a new LaunchDarkly feature: reusable user segments.

Changed

• The feature store interface has been changed to support user segment data as well as feature flags. Existing code that uses InMemoryFeatureStore or RedisFeatureStore should work as before, but custom feature store implementations will need to be updated.

2.5.0

2.5.0 (2018-02-12)

Added

• Adds support for a future LaunchDarkly feature, coming soon: semantic version user attributes.

Changed

• It is now possible to compute rollouts based on an integer attribute of a user, not just a string attribute.

2.4.1

[2.4.1] - 2018-01-23

Changed

• Reduce logging level for missing flags
• Relax json and faraday dependencies

Fixed

• Wrap redis bulk updates in a transaction
• Fixed documentation links

2.4.0

[2.4.0] - 2018-01-12

Changed

• Will use feature store if already initialized even if connection to service could not be established. This is useful when flags have been initialized in redis.
• Increase default and minimum polling interval to 30s
• Strip out unknown top-level attributes

2.3.2

[2.3.2] - 2017-12-02

Fixed

• Make sure redis store initializations are atomic

2.3.1

[2.3.1] - 2017-11-16

Added

• Add close method to Ruby client to stop processing events
• Add support for Redis feature store
• Add support for LDD mode
• Allow user to disable outgoing event stream.

Changed

• Stop retrying on 401 responses (due to bad sdk keys)