prepare 2.20.0 release #236
Merged
Conversation
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
refactor to isolate the sync XHR logic; expose close() method
add script to publish docs to Github Pages
fix uuid dependency, add unit tests for user key
change HTTP response handling to avoid CORS header errors
# Conflicts: # scripts/release-docs.sh # scripts/release.sh
don't use Promise.finally()
allow Electron and Node SDKs to report their own SDK version
…plates apply markdown templates
misc doc edits
add inlineUsersToEvents to TypeScript defs by updating js-sdk-common
…-warning don't log a warning about custom goal being unknown
…header Release js-client-sdk with the header transformation change
eli-darkly
approved these changes
Oct 15, 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.
[2.20.0] - 2021-10-15
Added:
LDOptions.requestHeaderTransformallows custom headers to be added to all HTTP requests. This may be necessary if you have an Internet gateway that uses a custom header for authentication. Note that custom headers may cause cross-origin browser requests to be rejected unless you have a way to ensure that the header name also appears inAccess-Control-Allow-Headersfor CORS preflight responses; if you are connecting to the LaunchDarkly Relay Proxy, it has a way to configure this.