v1.16.1 - Backwards compat to ruby 2.5.0

1.16.1 (#119)

v1.16.0 - Add support for DataStore

Add support for ruby 2.5.9

v1.14.0 - Async event flushing

• Fix bug where batched event logging was blocking the calling thread for flushes trigger by logging_max_buffer_size being hit.
• Add "evaluated_keys" to the client_initialize_response

v1.13.0 - new initialization options to bootstrap client SDKs and the server SDK

• added options related to bootstrapping the SDK:

• • bootstrap_values: pass a JSON string that represents the rulesets to bootstrap the SDK so that it can work even if Statsig backend is unreachable
• • rules_updated_callback: this callback is invoked whenever there are updated rulesets fetched by the SDK. It has 2 parameters, rules (string), and time (number) that represent the JSON rulesets and the freshness of it.

• added get_client_initialize_response API which returns a response for a user to be used to bootstrap a client SDK. To use it, simply pass in your user object, and pass the response as the initializeValues option when initializing your client SDKs.

• now the SDK logs evaluation details so that you can check in exposure stream whether a user got a certain value due to what reason, e.g. bootstrapped, uninitialized, etc.

• other internal improvements.

v1.12.0 - Adds localMode, overrides

Introduces a new StatsigOption: local_mode defaults to false. When set to true, it will shortcircuit all network requests to statsig servers. Therefore, initializing statsig with local_mode: true will lead to default values for gates (false) and configs/experiments ({} empty value on a DynamicConfig

If you need to force a certain experience or codepath, you can use the override apis:

Statsig.override_gate(<gate_name>, <gate_value>);
Statsig.override_config(<config_name>, <config_value_hash>);

Also fixes an issue where the initialize error_callback fired on all requests, and makes the error_callback fire on any subsequent failures as the SDK polls for changes.

v1.10.0 - concurrency improvements

• added some improvements for concurrency usage and tests
• relaxed the user ID hard requirement to allow null user ID when there is a custom ID

v1.9.2 - allow http gem to be v5.0+

Per customer request, allowed the http gem to be on major version 5.0+

v1.9.1 - Bug fixes for get_layer API

• The Statsig::Layer class was not being loaded for some users. The fix was to add an explicit 'require' for this class.
• Fixes consistency test when comparing value == fetch_from_server

v1.9.0 - Adding Support for Layers

Introduces get_layer API to Statsig, adding the ability to get values via a Layer configuration set on the Statsig Console. See docs.statsig.com/layers

v1.8.4 - fix version compare operator with invalid values

Previously if a version value is null or empty, it's parsed into a version of 0 effectively, which is inconsistent with how other languages/SDKs do it. This patch makes it so that a valid version value must be passed, or else the condition will fail.