5.2.3

[5.2.3] - 2021-02-19

Fixed:

• The flag update notification mechanism in FlagTracker did not work when the data source was FileData. This has been fixed so that whenever FileData reloads the data file(s) due to a file being modified, it signals that the flags were updated. The SDK will behave as if every flag was updated in this case, regardless of which part of the file data was actually changed, but it was already the case that a flag change event did not necessarily mean there was any significant change to the flag. You can use addFlagValueChangeListener (as opposed to addFlagChangeListener) to be notified only of changes that affect a specific flag's value for a specific user. (#224)

5.2.2

[5.2.2] - 2021-01-15

Fixed:

• Updated Guava from 28.2-jre to 30.1-jre to resolve CVE-2020-8908. This CVE did not affect the SDK as the SDK does not use the vulnerable functionality.

5.2.1

[5.2.1] - 2020-12-01

Fixed:

• TestData.FlagBuilder did not copy flags' targeting rules when applying an update to an existing test flag. (#220)

5.2.0

[5.2.0] - 2020-10-09

Added:

• Add support for setting a socketFactory in the HttpConfiguration builder. This is used to create sockets when initiating HTTP connections. For TLS connections sslSocketFactory is used.

5.1.1

[5.1.1] - 2020-09-30

Fixed:

• The com.launchdarkly.sdk.json.LDJackson class was not usable in the default distribution of the SDK (nor in the all distribution) because Jackson class names had been incorrectly modified by the shading step in the build. (#213)
• Setting custom base URIs for the streaming, polling, or events service could produce incorrect results if the URI had a context path. (Thanks, msafari!)
• Corrected format strings in some log messages. (#211)

4.14.4

[4.14.4] - 2020-09-28

Fixed:

• Restored compatibility with Java 7. A transitive dependency that required Java 8 had accidentally been included, and the CI build did not detect this because the tests were being run in Java 8 even though the compiler target was 7. CI builds now verify that the SDK really can run in Java 7. This fix is only for 4.x; the 5.x SDK still does not support Java 7.
• Bumped OkHttp version to 3.12.12 to avoid a crash on Java 8u252.
• Removed an obsolete comment that said the trackMetric method was not yet supported by the LaunchDarkly service; it is.

5.1.0

[5.1.0] - 2020-09-04

Added:

• The TestData class in com.launchdarkly.sdk.server.integrations is a new way to inject feature flag data programmatically into the SDK for testing—either with fixed values for each flag, or with targets and/or rules that can return different values for different users. Unlike FileData, this mechanism does not use any external resources, only the data that your test code has provided.

Fixed:

• In polling mode, the log message "LaunchDarkly client initialized" was appearing after every successful poll request. It should only appear once.

5.0.5

[5.0.5] - 2020-09-03

Fixed:

• Bump SnakeYAML from 1.19 to 1.26 to address CVE-2017-18640. The SDK only parses YAML if the application has configured the SDK with a flag data file, so it's unlikely this CVE would affect SDK usage as it would require configuration and access to a local file.

4.14.3

[4.14.3] - 2020-09-03

Fixed:

• Bump SnakeYAML from 1.19 to 1.26 to address CVE-2017-18640. The SDK only parses YAML if the application has configured the SDK with a flag data file, so it's unlikely this CVE would affect SDK usage as it would require configuration and access to a local file.

5.0.4

[5.0.4] - 2020-09-01

Fixed:

• Updated the version of OkHttp contained within the SDK from 4.5.0 to 4.8.1, to address multiple known issues including an incompatibility with OpenJDK 8.0.252 under some conditions. (#204)