Release 2.3.0

[2.3.0] - November 14, 2018

New Features

• Allow sticky bucketing via passing in attributes.$opt_experiment_bucket_map, this more easily allows customers to do some async data fetching and ensure a user gets a specific variation.

const userId = '123'
const expId = '456'
const variationId = '678'
const userAttributes = {
  $opt_experiment_bucket_map: {
    [expId]: {
      variation_id: variationId
    }
  }
}

var selectedVariationKey = optimizelyClient.activate('experiment-1', userId, userAttributes);

3.0.0-rc

This is the release candidate version of the 3.0 SDK:

New Features

• Support for boolean combinations of audiences on experiments (#175)
• Added PR template and commit message guidelines (#183)

Fixes

• Updated dependency versions (#180)
• Suppressed unwanted console output in tests (#181)
• Update project config to handle latest 3.0 datafile format (#182)

3.0.0-alpha

This is the alpha release of the 3.0 SDK, which includes a number of improvements to audience targeting:

New Features

• Support for number-valued and boolean-valued attributes (#174).
• Support for audiences with new match conditions for attribute values, including 'substring' and 'exists' matches for strings; 'greater than', 'less than', 'exact, and 'exists' matches for numbers; and "exact" and 'exists' matches for booleans (#174).

Breaking Changes

• Previously, when a 'not' audience condition was applied to a malformed attribute, it was possible for the condition to evaluate to true. We’ve corrected this behavior, so that malformed attributes always evaluate to null and are ignored (#174).

2.2.0

[2.2.0] - September 26, 2018

Fixed

• Track and activate should not remove null attributes (#168)
• Track attributes with valid attribute types (#166)
• Prevent SDK from initializing if the datafile version in invalid (#161)
• Updating lerna to latest version (#160)

Changed

• Change invalid experiment key to debug level (#165)

Release 2.1.3

[2.1.3] - August 21, 2018

Fixed

• Send all decisions for the same event in one snapshot. (#155)
• Give Node.js consumers the unbundled package (#133)

Deprecated

• The UMD build of the SDK now assigns the SDK namespace object to window.optimizelySdk rather than to window.optimizelyClient. The old name still works, but on its first access a deprecation warning is logged to the console. The alias will be removed in the 3.0.0 release. (#152)

2.1.2

chore(release): 2.1.2 (#126)

* Fix(nodejs/event_dispatcher): update error/resp handlers (#123)

- (nodejs) Prevent crash when `http`/`https` emits an error by adding an 'error' listener
- (nodejs) Fix `requestCallback` to conform to its role as a 'response' listener; notably, ensure it is called when the first argument is interpeted as the `http.IncomingMessage`, and _not_ called in the event of an error (as expected by `Optimizely#_sendImpressionEvent`/`Optimizely#track`).

Tested that this version (as 2.1.2-0) _does_ emit the messages expected in the demo app.

Fixes #122
Fixes #124

2.0.5

chore(release): 2.0.5 (#125)

* Fix(nodejs/event_dispatcher): update error/resp handlers (#123)

- (nodejs) Prevent crash when `http`/`https` emits an error by adding an 'error' listener
- (nodejs) Fix `requestCallback` to conform to its role as a 'response' listener; notably, ensure it is called when the first argument is interpeted as the `http.IncomingMessage`, and _not_ called in the event of an error (as expected by `Optimizely#_sendImpressionEvent`/`Optimizely#track`).

Tested that this version (as 2.1.2-0) _does_ emit the messages expected in the demo app.

Fixes #122
Fixes #124

2.1.1

chore: 2.1.1 release (#118)

* Fix impression sent from feature experiment variation toggled off. (#117)

2.0.4

chore: release 2.0.4 (#119)

* Fix impression sent from feature experiment variation toggled off. (#117)

2.1.0

• Introduces support for bot filtering. (#99)