Repository navigation
chore: Recommend using the latest patched Java release - #74
Merged
Merged
Conversation
Co-Authored-By: Jason Bailey <jbailey@launchdarkly.com>
Contributor
|
I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".
|
There was a problem hiding this comment.
Risk: low.
Automated risk review (dry run): Low
This PR would be automatically approved.
Why: This is a one-line README.md documentation change recommending the latest patched Java 11+ runtime; it does not alter code, CI, or approval policy.
If you disagree with this review, share this PR in #feedback-agent-approvals or submit a changes-requested review explaining why.
Sent by Cursor Approval Agent: Dry-Run PR Approver
kinyoklion
approved these changes
Nov 19, 2026
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
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.


Summary
Updates the supported Java version guidance in the README to state the minimum version while encouraging customers to run the latest patched version of a supported Java release, rather than the minimum.
Files changed:
README.mdContext
Prompted by a security review of a Ruby CVE. The same guidance is being added across LaunchDarkly SDK repositories that document a minimum language runtime version. The Ruby Server SDK wording is: "While this version of the LaunchDarkly SDK requires Ruby 3.1.0 or later, you should use the latest patched version of a supported Ruby release." Docs-only change.
Link to Devin session: https://app.devin.ai/sessions/141ab4fc650146aabc85c393f0b5b712
Open in Devin Desktop: https://app.devin.ai/desktop/session/141ab4fc650146aabc85c393f0b5b712?variant=devin
Requested by: @jsonbailey
Note
Overview
Updates Supported Java versions in
README.mdso it still states Java 11+ as the minimum but explicitly tells users to run the latest patched release of a supported Java line, matching security-focused guidance used in other LaunchDarkly SDK docs.Reviewed by Cursor Bugbot for commit dd11dee. Bugbot is set up for automated code reviews on this repo. Configure here.