This repository has been archived by the owner on May 30, 2024. It is now read-only.
Releases: launchdarkly/java-server-sdk
Releases · launchdarkly/java-server-sdk
6.2.0
[6.2.0] - 2023-06-13
Added:
- Custom headers can now be added to all HTTP requests with
Components.httpConfiguration().addCustomHeader
.
6.1.0
[6.1.0] - 2023-04-13
Added:
- Support for Payload Filtering in streaming and polling modes. Payload Filtering is a beta feature that allows SDKs to download a subset of environment data, rather than full environments. Please contact your account executive for more information.
5.10.8
[5.10.8] - 2023-03-21
Fixed:
- Updated snakeyaml to v2.0.0 to address CVE-2022-1471. This vulnerability would only have affected applications that used the FileData feature with a YAML file, assuming an attacker had write access to the filesystem.
6.0.6
[6.0.6] - 2023-03-20
Fixed:
- Updated snakeyaml to v2.0.0 to address CVE-2022-1471. This vulnerability would only have affected applications that used the FileData feature with a YAML file, assuming an attacker had write access to the filesystem.
6.0.5
[6.0.5] - 2023-02-01
Fixed:
- Segment bug that returns the default value for variation if multiple flag rules refer to the same segment with a rule.
6.0.4
[6.0.4] - 2023-01-10
Fixed:
- If the stream connection failed when the SDK had only partially received a piece of JSON data from the stream, the SDK was sometimes logging a misleading error message about invalid JSON in addition to the normal error message about the connection failure.
5.10.7
[5.10.7] - 2023-01-09
Fixed:
- If the stream connection failed when the SDK had only partially received a piece of JSON data from the stream, the SDK was sometimes logging a misleading error message about invalid JSON in addition to the normal error message about the connection failure.
6.0.3
[6.0.3] - 2023-01-06
Fixed:
- Fixed unintended error behavior when the SDK is being shut down, if streaming is enabled. The symptom was that 1. the SDK could log a misleading message about a network error (in reality this was just the connection being deliberately closed) and 2. an uncaught exception could be thrown from the worker thread that managed that connection. The uncaught exception would be ignored in a default JVM configuration, but it could have more serious consequences in an application that had configured a default exception handler to be triggered by all uncaught exceptions.
5.10.6
[5.10.6] - 2023-01-06
Fixed:
- Fixed unintended error behavior when the SDK is being shut down, if streaming is enabled. The symptom was that 1. the SDK could log a misleading message about a network error (in reality this was just the connection being deliberately closed) and 2. an uncaught exception could be thrown from the worker thread that managed that connection. The uncaught exception would be ignored in a default JVM configuration, but it could have more serious consequences in an application that had configured a default exception handler to be triggered by all uncaught exceptions.
6.0.2
[6.0.2] - 2023-01-04
Fixed:
- Fixed vulnerability CVE-2022-1471 which could allow arbitrary code execution if using
FileDataSource
with a YAML file. (Thanks, antonmos!)