v8.3.1

8.3.1 (2024-03-28)

Bug Fixes

• Ensure Rails.logger exists before using it (#258) (2f0f7ed)
• Remove invalid prereq check_variation_range check (#261) (#263) (74ca206), closes #260

v7.3.3

7.3.3 (2024-03-28)

Bug Fixes

• Remove invalid prereq check_variation_range check (#261) (960e392), closes #260

v8.3.0

8.3.0 (2024-03-14)

Features

• Inline contexts for all evaluation events (#245) (bd30c3b)
• Redact anonymous attributes within feature events (#246) (640ac39)

v8.2.0

8.2.0 (2024-02-20)

Features

• Enable gzip compression on polling requests (#249) (abffe47)

v8.1.0

8.1.0 (2024-01-03)

Features

• Add hash access and equality support to LDContext (#241) (1ba6bde)
• Define equality methods for LDContext and Reference (#232) (1b2ba7b)

Bug Fixes

• Calling stop in ldd mode no longer raises an exception (#237) (8149da1)

v7.3.2

7.3.2 (2023-12-26)

Bug Fixes

• Update missed version bump to LaunchDarkly::VERSION (#239) (dc44559)

v7.3.1

7.3.1 (2023-12-26)

Bug Fixes

• Calling stop in ldd mode no longer raises an exception (#235) (eeb9906)

8.0.0

[8.0.0] - 2023-10-17

The latest version of this SDK supports the ability to manage migrations or modernizations, using migration flags. You might use this functionality if you are optimizing queries, upgrading to new tech stacks, migrating from one database to another, or other similar technology changes. Migration flags are part of LaunchDarkly's Early Access Program. This feature is available to all LaunchDarkly customers but may undergo additional changes before it is finalized.

For detailed information about this version, refer to the list below. For information on how to upgrade from the previous version, read the migration guide.

Added:

• A new Migrator type which provides an out-of-the-box configurable migration framework.
• For more advanced use cases, added new migration_variation and track_migration_op methods on LDClient.

Removed:

• Ruby 2.7 support was removed.
• The legacy user format for contexts is no longer supported. To learn more, read the Contexts documentation.
• Previously deprecated config options user_keys_capacity, user_keys_flush_interval, private_attribute_names, default_user_keys_capacity, user_cache_size, user_cache_time, and default_user_keys_flush_interval have been removed.
• Previously deprecated test data flag builder methods variation_for_all_users, value_for_all_users, and clear_user_targets have been removed.

7.3.0

[7.3.0] - 2023-10-16

Fixed:

• The documentation for the default_connect_timeout setting stated it defaulted to 10 seconds when the code actually defaults to 2. (Thanks, zmagg-figma!)

Deprecated:

• Creating an LDContext using the legacy user format has been deprecated and will be removed in the next major release. To learn more, read the Contexts documentation.

7.2.0

[7.2.0] - 2023-05-04

Added:

• You can monitor the status of the SDK's data source (which normally means the streaming connection to the LaunchDarkly service) with LaunchDarkly::LDClient.data_source_status_provider. This allows you to check the current connection status, and to be notified if this status changes.
• You can monitor the status of a data store with LaunchDarkly::LDClient.data_store_status_provider. This allows you to check whether updates are succeeding and to be notified if this status changes.
• You can tell the SDK to notify you whenever a feature flag's configuration has changed (either in general, or in terms of its result for a specific context), using LaunchDarkly::LDClient.flag_tracker.