6.3.1

[6.3.1] - 2021-12-31

Fixed:

• Fixed a bug that could cause a streaming connection to fail intermittently if the feature flag data contained UTF-8 characters outside of the ASCII character set. This would happen if a multi-byte character happened to be split across two successive reads from the stream, so the chances of it happening varied according to how often international characters appeared in the data and how much buffering of reads was done by the OS.
• In JRuby only, stream reconnections would fail if the application explicitly set the initial reconnect delay to zero.

6.3.0

[6.3.0] - 2021-12-09

Added:

• The SDK now supports evaluation of Big Segments. See: https://docs.launchdarkly.com/home/users/big-segments
• LaunchDarkly::Integrations::TestData is a new way to inject feature flag data programmatically into the SDK for testing—either with fixed values for each flag, or with targets and/or rules that can return different values for different users. Unlike FileData, this mechanism does not use any external resources, only the data that your test code has provided.

Changed:

• To use the file data source feature, the preferred entry point is now LaunchDarkly::Integrations::FileData.data_source rather than LaunchDarkly::FileDataSource.factory. This makes the Ruby SDK more consistent with other SDKs, grouping together all of the optional "connecting the SDK to something else" features under Integrations, and using the method name data_source for consistency with the Config property that will receive the object.

Deprecated:

• LaunchDarkly::FileDataSource (see above).

6.2.5

[6.2.5] - 2021-10-12

Fixed:

• Fixed a bug that caused unnecessarily heavy CPU usage when receiving very large sets of flag data from LaunchDarkly.
• Improved the speed of making the initial streaming connection to LaunchDarkly. The delay that happens before reconnecting after a connection failure was mistakenly being applied before the first connection.

6.2.4

[6.2.4] - 2021-08-11

Changed:

• The dependency version constraint for the http gem is now looser: it allows 5.x versions as well as 4.x. The breaking changes in http v5.0.0 do not affect the SDK. (#184)
• The dependency version constraint for the json gem is also looser: it allows any 2.x version that is higher than the SDK's minimum dependency version, not just 2.3. (#184)
• The project's build now uses v2.2.10 of bundler due to known vulnerabilities in other versions.

6.2.3

[6.2.3] - 2021-08-06

Fixed:

• Diagnostic events did not properly set the usingProxy attribute when a proxy was configured with the HTTPS_PROXY environment variable. (#182)

6.2.2

[6.2.2] - 2021-07-23

Fixed:

• Enabling debug logging in polling mode could cause polling to fail with a NameError. (Thanks, mmurphy-notarize!)

6.2.1

[6.2.1] - 2021-07-15

Changed:

• If variation or variation_detail is called with a user object that has no key (an invalid condition that will always result in the default value being returned), the SDK now logs a warn-level message to alert you to this incorrect usage. This makes the Ruby SDK's logging behavior consistent with the other server-side LaunchDarkly SDKs. (#177)

6.2.0

[6.2.0] - 2021-06-17

Added:

• The SDK now supports the ability to control the proportion of traffic allocation to an experiment. This works in conjunction with a new platform feature now available to early access customers.

6.1.1

[6.1.1] - 2021-05-27

Fixed:

• Calling variation with a nil user parameter is invalid, causing the SDK to log an error and return a fallback value, but the SDK was still sending an analytics event for this. An event without a user is meaningless and can't be processed by LaunchDarkly. This is now fixed so the SDK will not send one.

6.1.0

[6.1.0] - 2021-02-04

Added:

• Added the alias method. This can be used to associate two user objects for analytics purposes by generating an alias event.