This repository has been archived by the owner on May 30, 2024. It is now read-only.
prepare 4.5.1 release #149
Merged
Conversation
This file contains 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
don't give up permanently after a 400 error
add brief Java compatibility note to readme
evaluate with an explanation - initial implementation
stop using deprecated TestFeatureStore in tests
avoid unnecessary retry after Redis update
…vents include explanations, if requested, in full feature request events
better error logging practices
test that flags loaded from a file actually work
… environment variable
…ation-for-java-android-sdks fix fossa integration
fix build script to ensure all of our packages are correctly included
log stream errors as WARN, not ERROR
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
[4.5.1] - 2018-11-21
Fixed:
com.launchdarkly.client.filespackage (the test file data source component added in v4.5.0) to be inaccessible unless you were using the "thin" jar.WARNlevel, rather thanERROR.