This repository was archived by the owner on May 30, 2024. It is now read-only.
prepare 6.4.1 release #245
Closed
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
use CircleCI for Windows build
# Conflicts: # test/requestor-test.js # test/streaming-test.js
…nosticsManager if needed
add more end-to-end tests, improve HTTP test helpers, general cleanup
change asyncify to promisifySingle
…itial diagnostic events, part 2: initial event and stats, except for stream inits
# Conflicts: # diagnostic_events.js
…ream diagnostic events, part 3: capture stream connection stats
…n-fixes minor fixes to config validation messages + add comment
# Conflicts: # messages.js
* don't ever use for...in * add null guard
* use TestData in our own tests * update TS interface * lint * typo
…-fix bump launchdarkly-eventsource dependency for sc-136154 fix
fix some evaluation edge cases
…riment fix allFlagsState behavior regarding experimentation
# Conflicts: # test/LDClient-evaluation-test.js
Co-authored-by: Eli Bishop <eli@launchdarkly.com>
…date update js-eventsource to 1.4.4 for security fix
remove package-lock.json
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
10 participants
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.4.1] - 2022-03-28
Removed:
package-lock.jsonfile is no longer in source control. As this is a library project, the lockfile never affected application code that used the SDK, but only affected the SDK's CI build. It is preferable for the CI build to refer only topackage.jsonso that it resolves dependencies the same way an application using the SDK would, rather than using pinned dependencies that an application would not use. This also prevents incorrect results from security scanners that, if a lockfile is present, will look only at the dependency versions in the lockfile (that is, the versions that were available at the time that that file was generated) rather than those that are currently available.