chore(main): release launchdarkly-java-server-sdk 7.17.1 - #216
Merged
kinyoklion merged 1 commit intoSep 16, 2026
Merged
kinyoklion merged 1 commit into
kinyoklion merged 1 commit into
Conversation
kinyoklion
approved these changes
Sep 16, 2026
kinyoklion
deleted the
release-please--branches--main--components--launchdarkly-java-server-sdk
branch
September 16, 2026 17:09
Contributor
Author
|
🤖 Created releases: 🌻 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 I have created a release beep boop
7.17.1 (2026-09-15)
Bug Fixes
This PR was generated with Release Please. See documentation.
Note
Overview
Releases
launchdarkly-java-server-sdk7.17.1 by bumping the package version in.release-please-manifest.json,gradle.properties, andVersion.SDK_VERSION, and adding the 7.17.1 changelog entry.The release ships the bug fix from #213: when
isFlagKnownruns before the client is initialized but the data store already has cached flag data, the “using last known values from data store” warning is emitted once perLDClientinstance instead of on every call. No other functional changes appear in this diff.Reviewed by Cursor Bugbot for commit 1f9019f. Bugbot is set up for automated code reviews on this repo. Configure here.