Skip to content

chore(main): release launchdarkly-java-server-sdk 7.18.2 - #271

Merged
kinyoklion merged 1 commit into
mainfrom
release-please--branches--main--components--launchdarkly-java-server-sdk
Nov 20, 2026
Merged

kinyoklion merged 1 commit into
mainfrom
release-please--branches--main--components--launchdarkly-java-server-sdk

Conversation

@github-actions

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

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

7.18.2 (2026-11-20)

Bug Fixes

  • Clear empty FDv2 selectors in shared protocol handling (#261) (576b081)
  • Prevent flags in a persistent store from becoming available to mobile keys (#275) (32c8676)
  • Treat a null optional property in flag data as omitted (#268) (3af465d)
  • Update launchdarkly-java-sdk-internal to 1.13.0 (#272) (9cc5885)

This PR was generated with Release Please. See documentation.


Note

Overview
This release PR bumps the LaunchDarkly Java server SDK from 7.18.1 to 7.18.2 across Release Please metadata (gradle.properties, Version.SDK_VERSION, and .release-please-manifest.json).

The new CHANGELOG section records the fixes shipped in this patch: clearing empty FDv2 selectors in shared protocol handling, blocking persistent-store flags from being exposed to mobile keys, treating null optional flag properties as omitted, and updating launchdarkly-java-sdk-internal to 1.13.0. Those behavioral changes are not part of this diff—only the version and release notes are updated here.

Reviewed by Cursor Bugbot for commit 9087581. 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 18, 2026 20:05
@cursor cursor Bot added the risk:low label Nov 18, 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.

Risk: low.

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: Release-please version bump of launchdarkly-java-server-sdk from 7.18.1 to 7.18.2 in Version.java, gradle.properties, the release-please manifest, and CHANGELOG.md, with no logic, infrastructure, or workflow changes.

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

@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--launchdarkly-java-server-sdk branch from 406d2b5 to ba82dbf Compare November 18, 2026 21:45

@kinyoklion kinyoklion left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Holding until after internal package update.

@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--launchdarkly-java-server-sdk branch from ba82dbf to 786433c Compare November 18, 2026 23:42
@tanderson-ld

Copy link
Copy Markdown
Contributor

You can release.

@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--launchdarkly-java-server-sdk branch 8 times, most recently from 6f675f6 to 5b5b48c Compare November 20, 2026 15:34
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--launchdarkly-java-server-sdk branch from 5b5b48c to 9087581 Compare November 20, 2026 16:01
@kinyoklion
kinyoklion merged commit b0fde73 into main Nov 20, 2026
6 checks passed
@kinyoklion
kinyoklion deleted the release-please--branches--main--components--launchdarkly-java-server-sdk branch November 20, 2026 19:36
@github-actions

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

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.

2 participants