Skip to content

Commit 61f6aad

Browse files
authored
chore: Release notes for 3.0.0-alpha release. (#226)
1 parent 6366bad commit 61f6aad

File tree

1 file changed

+18
-0
lines changed

1 file changed

+18
-0
lines changed

CHANGELOG.md

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,23 @@
11
# Optimizely Java X SDK Changelog
22

3+
## 3.0.0-alpha
4+
5+
October 10th, 2018
6+
7+
This is the alpha release of the 3.0 SDK, which includes a number of improvements to audience targeting along with a few bug fixes.
8+
9+
### New Features
10+
* Support for number-valued and boolean-valued attributes. ([#213](https://github.com/optimizely/java-sdk/pull/213))
11+
* 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.
12+
* Built-in datafile version compatibility checks so that SDKs will not initialize with a newer datafile it is not compatible with. ([#209](https://github.com/optimizely/java-sdk/pull/209))
13+
14+
### Breaking Changes
15+
* Previously, notification listeners filtered non-string attribute values from the data passed to registered listeners. To support our growing list of supported attribute values, we’ve changed this behavior. Notification listeners will now post any value type passed as an attribute. Therefore, the interface of the notification listeners has changed to accept a `Map<String, ?>`.
16+
* Update to use Java 1.7 ([#208](https://github.com/optimizely/java-sdk/pull/208))
17+
18+
### Bug Fixes
19+
* refactor: Performance improvements for JacksonConfigParser ([#209](https://github.com/optimizely/java-sdk/pull/209))
20+
321
## 2.1.3
422

523
September 21st, 2018

0 commit comments

Comments
 (0)