This repository was archived by the owner on May 30, 2024. It is now read-only.
prepare 6.0.0 release #223
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
…ulnerability with 'extend' (#140) * bump request to resolve a security vulnerability with extend * remove incorrect build step * update language
# Conflicts: # package-lock.json # package.json
update doc comment for track() with metricValue
# Conflicts: # CHANGELOG.md
fix ruleIndex in rule match reason
Migrate to ES2015 syntax and add linting
# Conflicts: # feature_store_event_wrapper.js
# Conflicts: # .circleci/config.yml
(6.0) allow feature store to be specified as a factory (so it can get our logger)
(6.0) update lots of dependencies
bwoskow-ld
approved these changes
Jun 17, 2021
# Conflicts: # .gitignore # package-lock.json # package.json
LaunchDarklyReleaseBot
pushed a commit
that referenced
this pull request
Dec 10, 2021
…om-errors explicitly enable jsdom types in TypeScript build to avoid errors when jsdom is referenced for some reason
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.
[6.0.0] - 2021-06-17
This major version release is for updating Node.js compatibility, simplifying the SDK's dependencies, and removing deprecated names.
Except for the dependency changes described below which may require minor changes in your build, and a minor new logging feature, usage of the SDK has not changed in this release. For more details about changes that may be necessary, see the 5.x to 6.0 migration guide.
Dropping support for obsolete Node.js versions makes it easier to maintain the SDK and keep its dependencies up to date. See LaunchDarkly's End of Life Policy regarding platform version support.
Simplifying dependencies reduces the size of the SDK bundle, as well as reducing potential compatibility problems and vulnerabilities. The total size of the SDK code plus its dependency tree, not including any of the optional database integrations, has been reduced by nearly 75%.
Added:
ld.basicLogger, allowing customization of the SDK's default logging behavior without having to provide a fullLDLoggerimplementation.Changed:
Removed:
redispackage.ld.basicLoggerimplementation, which uses the same format as the previous default Winston configuration, so again there should be no visible difference. Note: If you are using thelaunchdarkly-node-server-sdk-dynamodborlaunchdarkly-node-server-consuldatabase integration packages, you should update them to the latest versions which have also had the Winston dependency removed.yaml. This package was only used for the optional file data source functionality. You can still use YAML data files with the file data source if you explicitly install theyamlpackage in your project; the SDK will automatically detect its presence.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.