launchdarkly-node-client-sdk 3.0.1 → 3.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,10 @@
1
+ name: 'Close stale issues and PRs'
2
+ on:
3
+ workflow_dispatch:
4
+ schedule:
5
+ # Happen once per day at 1:30 AM
6
+ - cron: '30 1 * * *'
7
+
8
+ jobs:
9
+ sdk-close-stale:
10
+ uses: launchdarkly/gh-actions/.github/workflows/sdk-stale.yml@main
package/CHANGELOG.md CHANGED
@@ -2,12 +2,16 @@
2
2
 
3
3
  All notable changes to the LaunchDarkly Client-Side SDK for Node.js will be documented in this file.
4
4
 
5
- ## [3.0.0] - 2023-01-12
6
- The latest version of this SDK supports LaunchDarkly's new custom contexts feature. Contexts are an evolution of a previously-existing concept, "users." Contexts let you create targeting rules for feature flags based on a variety of different information, including attributes pertaining to users, organizations, devices, and more. You can even combine contexts to create "multi-contexts."
5
+ ## [3.0.2] - 2023-03-21
6
+ ### Changed:
7
+ - Update `LDContext` to allow for key to be optional. This is used when making an anonymous context with a generated key.
7
8
 
8
- This feature is only available to members of LaunchDarkly's Early Access Program (EAP). If you're in the EAP, you can use contexts by updating your SDK to the latest version and, if applicable, updating your Relay Proxy. Outdated SDK versions do not support contexts, and will cause unpredictable flag evaluation behavior.
9
+ ## [3.0.1] - 2023-02-15
10
+ ### Changed:
11
+ - Upgrade to `js-sdk-common` version `5.0.2`. This removes usage of optional chaining (`?.`) to allow for use with older transpilers.
9
12
 
10
- If you are not in the EAP, only use single contexts of kind "user", or continue to use the user type if available. If you try to create contexts, the context will be sent to LaunchDarkly, but any data not related to the user object will be ignored.
13
+ ## [3.0.0] - 2023-01-12
14
+ The latest version of this SDK supports LaunchDarkly's new custom contexts feature. Contexts are an evolution of a previously-existing concept, "users." Contexts let you create targeting rules for feature flags based on a variety of different information, including attributes pertaining to users, organizations, devices, and more. You can even combine contexts to create "multi-contexts."
11
15
 
12
16
  For detailed information about this version, please refer to the list below. For information on how to upgrade from the previous version, please read the [migration guide](https://docs.launchdarkly.com/sdk/client-side/node-js/migration-2-to-3).
13
17
 
package/CODEOWNERS ADDED
@@ -0,0 +1,2 @@
1
+ # Repository Maintainers
2
+ * @launchdarkly/team-sdk
package/README.md CHANGED
@@ -10,7 +10,7 @@ For using LaunchDarkly in *server-side* Node.js applications, refer to our [Serv
10
10
 
11
11
  ## LaunchDarkly overview
12
12
 
13
- [LaunchDarkly](https://www.launchdarkly.com) is a feature management platform that serves over 100 billion feature flags daily to help teams build better software, faster. [Get started](https://docs.launchdarkly.com/home/getting-started) using LaunchDarkly today!
13
+ [LaunchDarkly](https://www.launchdarkly.com) is a feature management platform that serves trillions of feature flags daily to help teams build better software, faster. [Get started](https://docs.launchdarkly.com/home/getting-started) using LaunchDarkly today!
14
14
 
15
15
  [![Twitter Follow](https://img.shields.io/twitter/follow/launchdarkly.svg?style=social&label=Follow&maxAge=2592000)](https://twitter.com/intent/follow?screen_name=launchdarkly)
16
16
 
package/SECURITY.md ADDED
@@ -0,0 +1,5 @@
1
+ # Reporting and Fixing Security Issues
2
+
3
+ Please report all security issues to the LaunchDarkly security team by submitting a bug bounty report to our [HackerOne program](https://hackerone.com/launchdarkly?type=team). LaunchDarkly will triage and address all valid security issues following the response targets defined in our program policy. Valid security issues may be eligible for a bounty.
4
+
5
+ Please do not open issues or pull requests for security issues. This makes the problem immediately visible to everyone, including potentially malicious actors.
@@ -24,6 +24,8 @@ app.get('/', (req, res) => {
24
24
  'service-endpoints',
25
25
  'tags',
26
26
  'user-type',
27
+ 'inline-context',
28
+ 'anonymous-redaction',
27
29
  ],
28
30
  });
29
31
  });
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "launchdarkly-node-client-sdk",
3
- "version": "3.0.1",
3
+ "version": "3.1.0",
4
4
  "description": "LaunchDarkly Client-Side SDK for Node.js",
5
5
  "author": "LaunchDarkly <team@launchdarkly.com>",
6
6
  "license": "Apache-2.0",
@@ -65,7 +65,7 @@
65
65
  },
66
66
  "dependencies": {
67
67
  "launchdarkly-eventsource": "1.4.3",
68
- "launchdarkly-js-sdk-common": "5.0.2",
68
+ "launchdarkly-js-sdk-common": "5.1.0",
69
69
  "node-localstorage": "^1.3.1"
70
70
  },
71
71
  "repository": {