Skip to content

chore(main): release launchdarkly-java-sdk-internal 1.14.0 - #280

Merged
tanderson-ld merged 1 commit into
mainfrom
release-please--branches--main--components--launchdarkly-java-sdk-internal
Nov 20, 2026
Merged

tanderson-ld merged 1 commit into
mainfrom
release-please--branches--main--components--launchdarkly-java-sdk-internal

Conversation

@github-actions

@github-actions github-actions Bot commented Nov 20, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

1.14.0 (2026-11-20)

Features

  • replace permanent event-delivery disable with a bounded cooldown (#256) (f77bf78)

This PR was generated with Release Please. See documentation.


Note

Overview
Release-only PR that cuts launchdarkly-java-sdk-internal 1.14.0: bumps lib/shared/internal/gradle.properties, .release-please-manifest.json, and adds the 1.14.0 section to CHANGELOG.md.

The new changelog entry documents the headline feature already merged for this release: event delivery no longer stays permanently disabled after failures; it uses a bounded cooldown instead (DeliveryCooldownTracker in the event processor).

Reviewed by Cursor Bugbot for commit bb67741. Bugbot is set up for automated code reviews on this repo. Configure here.

@github-actions
github-actions Bot requested a review from a team as a code owner November 20, 2026 15:34
@cursor cursor Bot added the risk:low label Nov 20, 2026

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Automated risk review (dry run): Low

This PR would be automatically approved. Because it was authored by a bot, a human approving review would also be required.

Why: This PR only bumps launchdarkly-java-sdk-internal from 1.13.1 to 1.14.0 in lib/shared/internal/gradle.properties and .release-please-manifest.json, and adds a CHANGELOG entry. No application, CI, or behavior code is changed.

If you disagree with this review, share this PR in #feedback-agent-approvals or submit a changes-requested review explaining why.

Open in Web View Automation 

Sent by Cursor Approval Agent: Dry-Run PR Approver

@tanderson-ld
tanderson-ld merged commit 6da79c0 into main Nov 20, 2026
39 of 42 checks passed
@tanderson-ld
tanderson-ld deleted the release-please--branches--main--components--launchdarkly-java-sdk-internal branch November 20, 2026 16:01
@github-actions

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

tanderson-ld added a commit that referenced this pull request Nov 20, 2026
## What

Adopts the event-delivery cooldown (EVTPROC Section 1.8,
launchdarkly/sdk-specs#278) in the server SDK by picking up
launchdarkly-java-sdk-internal 1.14.0, which replaces the permanent
disable-on-unexpected-delivery-failure with bounded, self-recovering
cooldown windows (see the internal module PR #256 for the behavior
itself).

- Bumps `launchdarklyJavaSdkInternal` to 1.14.0.
- Migrates the internal `EventSenderWrapper` off the deprecated internal
`Result` constructor onto the new factories (`SUCCESS` to
`success(null)`, `FAILURE` to `failure()`, `STOP` to
`unexpectedFailure()`), and adds the previously missing unit coverage
for that mapping. This is the one behavioral change in the server
module: a custom `EventSender` returning `STOP` now drives a bounded
cooldown rather than a permanent stop.
- Leaves the public `subsystems.EventSender.Result.STOP` enum and its
javadoc unchanged. `STOP` is still the public signal for an unexpected
delivery failure; the cooldown is the SDK's internal response to it,
documented in the internal module and the release notes rather than in
this interface doc.
- Advertises the `event-delivery-cooldown` capability in the contract
test service, activating the `events/delivery cooldown` tests.
- The 413 contract test runs unsuppressed: the locally-unrecoverable 413
carve-out landed in 1.14.0 (#256), so a 413 drops only the oversized
payload without entering cooldown, and the test passes.
- The data sources' uses of the deprecated boolean HTTP-error helpers
are deliberately untouched; the FDv2 implementations' migration to the
classifier is a separate follow-up.

## Dependencies (both gates cleared)

1. launchdarkly-java-sdk-internal 1.14.0 is released (#280 merged; on
Maven Central).
2. sdk-test-harness 2.44.0 ships the cooldown tests (#526) with the
configurer-ordering fix.

## Verification

Built and tested against the released 1.14.0: the server module
compiles, checkstyle is clean, and the `EventSenderWrapper` mapping
tests pass (STOP to unexpectedFailure, FAILURE to ordinary failure,
SUCCESS to delivered, and the diagnostic path using the same mapping).
The full `events/` contract suite runs in CI against the released
harness.

## Release notes

- Minor (feat). Behavior change worth calling out: event delivery no
longer shuts down permanently on an unexpected error such as an invalid
SDK key; it backs off in windows from 5 minutes up to 1 hour, probing
again after each window, and returns to the normal delivery schedule as
soon as a probe succeeds. A custom `EventSender` returning `STOP` now
causes the same bounded cooldown.

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Overview**
> This PR **adopts event-delivery cooldown** in the Java server SDK by
upgrading **`launchdarkly-java-sdk-internal` to 1.14.0**. Unexpected
delivery failures (e.g. custom `EventSender` returning `STOP`) now
trigger **bounded backoff and recovery** instead of permanently shutting
down event delivery.
> 
> The server’s **`EventSenderWrapper`** is updated to use the internal
**`Result` factory APIs** (`failure()`, `unexpectedFailure()`,
`success(null)`) so `STOP` maps to unexpected failure and plugs into the
new cooldown behavior in the internal event processor.
> 
> The contract test service **advertises `event-delivery-cooldown`**,
enabling harness cooldown tests. **Unit tests** cover success, ordinary
failure, and `STOP` mapping for both analytics and diagnostic sends.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
2598dcf. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant