prepare 7.2.0 release #218
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
don't let user fall outside of last bucket in rollout
# Conflicts: # lib/ldclient-rb/evaluation.rb # spec/evaluation_spec.rb
(6.0 - #1) refactor evaluation logic and move it out of the main namespace
(6.0 - #2) make EvaluationReason an immutable class
(6.0 - #3) precompute evaluation reasons when we receive a flag
(6.0 - #4) rename FeatureStore to DataStore
add event payload ID header
(6.0) drop support for old Ruby versions
remove rake dependency
update ruby-eventsource to 1.0.3 for backoff bug
fix incorrect initialization of EventProcessor
…heck remove install-time openssl check that breaks if you don't have rake
There are multiple places throughout the code where we are still referencing users. I have tried to update all the places where a rename seems reasonable or appropriate. There is still some work to do in the test flag builders, but that will be done in a subsequent commit.
The new relic integration was removed many versions ago but a small trace remained behind.
Co-authored-by: Eli Bishop <eli@launchdarkly.com>
Merge u2c work into main branch
…for segmentMatch (#236)
When we introduced models for the flag and segment data, we added to_json methods which proxy to the underlying to_json method provided by the `json` gem. We defined the method with a variadic parameter, but we failed to unpack it when passing it on to the underlying implementation. This resulted in a serialization failure which prevented the redis data store from initializing.
The underlying event source library had an issue where, in certain environments, content-type header detection was failing. This was resolved in v2.2.2 of the event source gem.
The client instance will now provide access to a `data_source_status_provider`. This provider allows developers to retrieve the status of the SDK on demand, or asynchronously by registering listeners.
The full unit test suite includes tests relying on externally instances of Redis, Consult, and DynamoDB. By default, we do not want to run these tests. Rather, they should be opt-in by setting the environment variable `LD_SKIP_DATABASE_TESTS=0`.
The client instance will now provide access to a `flag_tracker`. This tracker allows developers to be notified when a flag configuration changes (or optionally when the /value/ of a flag changes for a particular context).
The client instance will now provide access to a `data_store_status_provider`. This provider allows developers to retrieve the data store status of the SDK on demand, or asynchronously by registering listeners.
louis-launchdarkly
approved these changes
May 3, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[7.2.0] - 2023-05-03
Added:
LaunchDarkly::LDClient.data_source_status_provider. This allows you to check the current connection status, and to be notified if this status changes.LaunchDarkly::LDClient.data_store_status_provider. This allows you to check whether updates are succeeding and to be notified if this status changes.LaunchDarkly::LDClient.flag_tracker.