3.0.3

What's Changed

• fix: [FFM-12712]: Bumps harness_ff_erlang_client_api to fix a problem with lowercase Content-Type headers not parsing correctly by @andybharness in #64

New Contributors

• @andybharness made their first contribution in #64

Full Changelog: 3.0.2...3.0.3

3.0.2

What's Changed

• FFM-12078 Bump mochiweb and client api by @erdirowlands in #63

Full Changelog: 3.0.1...3.0.2

3.0.1

What's Changed

• FFM-12000 Fixes an issue where a flag or target group change would not be stored with error Outdated by @erdirowlands in #62

Full Changelog: 3.0.0...3.0.1

3.0.0

What's Changed

• FFM-9927 - ** Breaking Percentage Rollout Changes **
  • The percentage rollout hash algorithm was slightly different compared to other Feature Flags SDKs, which resulted in a different bucket allocation for the same target. The overall distribution was the same, but this change ensures that the same target will get the same allocation per SDK
  • if a custom BucketBy field is set on the web app, but it can't be found in a target, then the SDK will fall back to bucketing by target identifier for that target a warning will be logged

Full Changelog: 2.0.1...3.0.0

2.0.2-rc.3

Fixes incorrect readme instructions for enabling rollout flagID hashing.

2.0.2-rc.2

Experimental support for modifying the percentage rollout hash:

1. Hashing the flag identifier first before appending it to the target identifier. The combination of target identifier and hashed flag identifier is then hashed again, before bucketing the target.
2. Multiply the hash by a user defined number, e.g. a prime number like 17, before bucketing the target.

Both of the above options can be enabled at the same time, if required.

For details, see https://github.com/harness/ff-erlang-server-sdk/tree/2.0.2-rc.2#percentage-rollout-experimental-features

2.0.2-rc.1

Experimental support for adding the name of the flag to the percentage rollout hash.

2.0.1

Fixes

• Some SDK dependencies were not getting included in releases created by mix

2.0.0

** Breaking for Erlang applications (not affecting Elixir applications) **

• Due to a new dependency on a murmur3 hashing library implemented in Elixir, the following is now required to use the SDK in Erlang applications:

  • Elixir is now required to be installed on your build system when compiling your application. Version 1.13.4 and above is required.
  • Rebar3 rebar_mix plugin installed in your Rebar3 plugins
  • For full details, see the Erlang SDK reference

• Please note that no further action is required for Elixir applications after upgrading the SDK to version 2.0.0

Enhancements

• Implemented retry logic for authentication, polling, and metrics services for resilience and fault tolerance.
• Changes supervisor

Fixes

• Swaps out murmur3 nif library which was giving unpredictable runtime behaviour in favour of pure Elixir implementation

1.2.1

Enhancements

• The optional configuration option introduced in 1.2.0 would only work if the application level was set to info - this change now sets the cfclient_evaluation module to info level if verbose_evaluation_logs is enabled.

See enable verbose evaluation logging for details

Full Changelog: 1.2.0...1.2.1