-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
prepare 6.2.1 release #142
Merged
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
support new filtering properties for client-side/mobile flags
This reverts commit 885691b.
(v6 - #7) reorganization and expansion of readme content
(v6 - #8) use configtypes library for config validation
(v6 - #9) create RelayCore and move most of the core logic into it
(v6 - #10) logic for adding/removing environments dynamically
(v6 - #11) factor out application startup code
(v6 - #12) cleaner encapsulation of stream logic
(v6 - #13) simplify context management, don't use a separate type for client-side context info
(v6 - #14) move some things into core subpackages, expose fewer impl details
(v6 - #15) move standard Relay into its own package, run endpoint tests more generically
(v6 - #16) move more things into core package
(v6 - #17) move even more things into core packages
(v6 - #18) move all remaining core stuff into core, clean up tests, move Relay app starter to main package
(v6 - #19) apply our standard linters, general code cleanup, doc comments
environment should still be usable even if the client timed out
recognize alias events from non-v3-schema payloads and forward them unchanged
bump dependency versions for SDK fixes
update go-server-sdk-dynamodb to get newer AWS SDK
…ted in requests (#244)
don't return 503 if SDK initialization has timed out
update SDK dependencies for JSON number parsing bugfix
bwoskow-ld
approved these changes
Jun 3, 2021
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.
[6.2.1] - 2021-06-03
Fixed:
1e5
). Since there are several equally valid number formats in JSON (so1e5
is exactly equivalent to100000
), whether this bug showed up would depend on the format chosen by whatever software had most recently converted the number to JSON before it was re-read, which is hard to predict, but it would only be likely to happen with either integers that had more than four trailing zeroes or floating-point numbers with leading zeroes. This bug also existed in the LaunchDarkly Go SDK prior to version 5.3.1, so anyone who uses both the Relay Proxy and the Go SDK should update both.