Update dependency com.launchdarkly:launchdarkly-java-server-sdk to v7

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
com.launchdarkly:launchdarkly-java-server-sdk	5.10.9 -> 7.5.0

---

Release Notes

launchdarkly/java-server-sdk (com.launchdarkly:launchdarkly-java-server-sdk)

v7.4.1

Compare Source

Added:

• Adds warning log if excessive start wait time is used.

Fixed:

• Improved preprocessing allocations to reduce memory footprint in rare flag configurations.

v7.4.0

Compare Source

Added:

• This release introduces a Hooks API. Hooks are collections of user-defined callbacks that are executed by the SDK at various points of interest. You can use them to augment the SDK with metrics or tracing.

v7.3.0

Compare Source

Changed:

• Redact anonymous attributes within feature events
• Always inline contexts for feature events

v7.2.6

Compare Source

Added:

• LDReactorClient to adapt LDClient to reactive streams.

v7.1.1

Compare Source

Fixed:

• Fixes NPE when interacting with Context created by copying. (Thanks,
  pedroafonsodias)

v7.1.0

Compare Source

Added:

• Added an improved way of setting wrapper information for wrapper SDKs. This functionality is primarily intended for use by LaunchDarkly while developing wrapper SDKs.

v7.0.0

Compare Source

The latest version of this SDK supports the ability to manage migrations or modernizations, using migration flags. You might use this functionality if you are optimizing queries, upgrading to new tech stacks, migrating from one database to another, or other similar technology changes. Migration flags are part of LaunchDarkly's Early Access Program. This feature is available to all LaunchDarkly customers but may undergo additional changes before it is finalized.

For detailed information about this version, refer to the list below. For information on how to upgrade from the previous version, read the migration guide.

Added:

• A new Migration type which provides an out-of-the-box configurable migration framework.
• For more advanced use cases, added new migrationVariation and trackMigration methods on LDClient.

Removed:

• Remove support for LDUser in LDClient methods. The LDContext.fromUser method can be used to convert an LDUser to an LDContext. In a future version it may be removed.

v6.3.0

Compare Source

[6.3.0] - 2023-10-16

Deprecated:

• Deprecated methods which take the LDUser type. These methods are removed in 7.0.0. Currently an LDUser can be converted to a LDContext using LDContext.fromUser. The ability to do this conversion may be removed in a future version.

v6.2.1

Compare Source

Changed:

• Bumping Guava version to incorporate CVE-2023-2976 fixes.

v6.2.0

Compare Source

Added:

• Custom headers can now be added to all HTTP requests with Components.httpConfiguration().addCustomHeader.

v6.1.0

Compare Source

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.

v6.0.6

Compare Source

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.

v6.0.5

Compare Source

Fixed:

• Segment bug that returns the default value for variation if multiple flag rules refer to the same segment with a rule.

v6.0.4

Compare Source

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.

v6.0.3

Compare Source

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.

v6.0.2

Compare Source

Fixed:

• Fixed vulnerability CVE-2022-1471 which could allow arbitrary code execution if using FileDataSource with a YAML file. (Thanks, antonmos!)

v6.0.1

Compare Source

Changed:

• The internal implementation of the SSE client for streaming updates has been revised to use a single worker thread instead of two worker threads, reducing thread contention and memory usage.

v6.0.0

Compare Source

The latest version of this SDK supports LaunchDarkly's new custom contexts feature. Contexts are an evolution of a previously-existing concept, "users." Contexts let you create targeting rules for feature flags based on a variety of different information, including attributes pertaining to users, organizations, devices, and more. You can even combine contexts to create "multi-contexts."

For detailed information about this version, please refer to the list below. For information on how to upgrade from the previous version, please read the migration guide.

Added:

• In com.launchDarkly.sdk, the types LDContext and ContextKind define the new context model.
• For all SDK methods that took an LDUser parameter, there is now an overload that takes an LDContext. The SDK still supports LDUser for now, but LDContext is the preferred model and LDUser may be removed in a future version.
• The TestData flag builder methods have been extended to support now context-related options, such as matching a key for a specific context type other than "user".

Changed (breaking changes from 6.x):

• It was previously allowable to set a user key to an empty string. In the new context model, the key is not allowed to be empty. Trying to use an empty key will cause evaluations to fail and return the default value.
• There is no longer such a thing as a secondary meta-attribute that affects percentage rollouts. If you set an attribute with that name in an LDContext, it will simply be a custom attribute like any other.
• The anonymous attribute in LDUser is now a simple boolean, with no distinction between a false state and a null state.
• Types such as DataStore, which define the low-level interfaces of LaunchDarkly SDK components and allow implementation of custom components, have been moved out of the interfaces subpackage into a new subsystems subpackage. Some types have been removed by using generics: for instance, the interface DataSourceFactory has been replaced by ComponentConfigurer<DataSource>. Application code normally does not refer to these types except possibly to hold a value for a configuration property such as LDConfig.Builder.dataStore(), so this change is likely to only affect configuration-related logic.

Changed (requirements/dependencies/build):

• The SDK no longer has a dependency on SLF4J. It will still use SLF4J as the default logging framework if SLF4J is in the classpath, so it is the application's responsibility to declare its own dependency on SLF4J, as any application that uses SLF4J would normally do.
• Applications that use the database integrations for Redis, DynamoDB, or Consul must update to the latest major versions of the corresponding packages (launchdarkly-java-server-sdk-redis-store, etc.).

Changed (behavioral changes):

• If SLF4J is not in the classpath, the SDK now uses System.err as its default logging destination. See "requirements/dependencies/build" above.
• The SDK can now evaluate segments that have rules referencing other segments.
• Analytics event data now uses a new JSON schema due to differences between the context model and the old user model.

Removed:

• Removed all types, fields, and methods that were deprecated as of the most recent 5.x release.
• Removed the secondary meta-attribute in LDUser and LDUser.Builder.
• The alias method no longer exists because alias events are not needed in the new context model.
• The inlineUsersInEvents option no longer exists because it is not relevant in the new context model.

---

Configuration

📅 Schedule: Branch creation - "after 7am and before 11am every weekday" in timezone Europe/London, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.