Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Bump semver and launchdarkly-node-server-sdk #14

Open
wants to merge 1 commit into
base: seed
Choose a base branch
from
Open

Bump semver and launchdarkly-node-server-sdk #14

wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Jun 25, 2023

Bumps semver to 7.5.3 and updates ancestor dependency launchdarkly-node-server-sdk. These dependencies need to be updated together.

Updates semver from 6.3.0 to 7.5.3

Release notes

Sourced from semver's releases.

v7.5.3

7.5.3 (2023-06-22)

Bug Fixes

Documentation

v7.5.2

7.5.2 (2023-06-15)

Bug Fixes

v7.5.1

7.5.1 (2023-05-12)

Bug Fixes

v7.5.0

7.5.0 (2023-04-17)

Features

Bug Fixes

v7.4.0

7.4.0 (2023-04-10)

Features

Bug Fixes

... (truncated)

Changelog

Sourced from semver's changelog.

7.5.3 (2023-06-22)

Bug Fixes

Documentation

7.5.2 (2023-06-15)

Bug Fixes

7.5.1 (2023-05-12)

Bug Fixes

7.5.0 (2023-04-17)

Features

Bug Fixes

7.4.0 (2023-04-10)

Features

Bug Fixes

... (truncated)

Commits
  • 7fdf1ef chore: release 7.5.3
  • bf53dd8 docs: add example for > comparator (#569)
  • abdd93d fix: set max lengths in regex for numeric and build identifiers (#571)
  • e7b78de chore: release 7.5.2
  • 58c791f fix: diff when detecting major change from prerelease (#566)
  • 5c8efbc fix: preserve build in raw after inc (#565)
  • 717534e fix: better handling of whitespace (#564)
  • 2f738e9 chore: bump @​npmcli/template-oss from 4.14.1 to 4.15.1 (#558)
  • aa016a6 chore: release 7.5.1
  • d30d25a fix: show type on invalid semver error (#559)
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by npm-cli-ops, a new releaser for semver since your current version.


Updates launchdarkly-node-server-sdk from 5.13.4 to 7.0.1

Release notes

Sourced from launchdarkly-node-server-sdk's releases.

7.0.1

[7.0.1] - 2023-02-08

Fixed:

  • Updated the async package dependency. The previous version of async was flagged in CVE-2021-43138

7.0.0

[7.0.0] - 2022-12-07

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."

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.

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.

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.

Added:

  • The types LDContext, LDSingleKindContext, and LDMultiKindContext define the new "context" model.
  • All SDK methods that took an LDUser parameter now take an LDContext. LDUser is now a subset of LDContext, so existing code based on users will still work.
  • Added contextKeysCapacity and contextKeysFlushInterval to LDOptions these supersede the equivalent user options.

Changed (breaking changes from 6.x):

  • There is no longer such a thing as a secondary meta-attribute that affects percentage rollouts. If you set an attribute with that name in LDContext, it will simply be a custom attribute like any other.
  • Evaluations now treat the anonymous attribute as a simple boolean, with no distinction between a false state and an undefined state.
  • LDClient.getUser has been replaced with LDClient.getContext.
  • privateAttributeNames has been replaced with privateAttributes in LDOptions. Private attributes now allow using attribute references.

Changed (behavioral changes):

  • Analytics event data now uses a new JSON schema due to differences between the context model and the old user model.

Removed:

  • Removed all types, fields, and methods that were deprecated as of the most recent 6.x release.
  • Removed the secondary meta-attribute in LDUser.
  • The alias method no longer exists because alias events are not needed in the new context model.
  • The inlineUsersInEvents options no longer exist because they are not relevant in the new context model.

Deprecated:

  • Deprecated userKeysCapacity and userKeysFlushInterval in LDOptions. New context equivalents have been added.

6.4.3

[6.4.3] - 2022-09-06

Fixed:

  • The TestDataRuleBuilder was using an incorrect field name for operators, which would prevent rules from working correctly with the TestData feature. (Thanks, LiamMorrow!)

6.4.2

[6.4.2] - 2022-06-06

Changed:

  • Enforce a 64 character limit for application.id and application.version configuration options.

6.4.1

[6.4.1] - 2022-04-26

... (truncated)

Changelog

Sourced from launchdarkly-node-server-sdk's changelog.

[7.0.1] - 2023-02-08

Fixed:

  • Updated the async package dependency. The previous version of async was flagged in CVE-2021-43138

[7.0.0] - 2022-12-07

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."

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.

Added:

  • The types LDContext, LDSingleKindContext, and LDMultiKindContext define the new "context" model.
  • All SDK methods that took an LDUser parameter now take an LDContext. LDUser is now a subset of LDContext, so existing code based on users will still work.
  • Added contextKeysCapacity and contextKeysFlushInterval to LDOptions these supersede the equivalent user options.

Changed (breaking changes from 6.x):

  • There is no longer such a thing as a secondary meta-attribute that affects percentage rollouts. If you set an attribute with that name in LDContext, it will simply be a custom attribute like any other.
  • Evaluations now treat the anonymous attribute as a simple boolean, with no distinction between a false state and an undefined state.
  • LDClient.getUser has been replaced with LDClient.getContext.
  • privateAttributeNames has been replaced with privateAttributes in LDOptions. Private attributes now allow using attribute references.

Changed (behavioral changes):

  • Analytics event data now uses a new JSON schema due to differences between the context model and the old user model.

Removed:

  • Removed all types, fields, and methods that were deprecated as of the most recent 6.x release.
  • Removed the secondary meta-attribute in LDUser.
  • The alias method no longer exists because alias events are not needed in the new context model.
  • The inlineUsersInEvents options no longer exist because they are not relevant in the new context model.

Deprecated:

  • Deprecated userKeysCapacity and userKeysFlushInterval in LDOptions. New context equivalents have been added.

[6.4.3] - 2022-09-06

Fixed:

  • The TestDataRuleBuilder was using an incorrect field name for operators, which would prevent rules from working correctly with the TestData feature. (Thanks, LiamMorrow!)

[6.4.2] - 2022-06-06

Changed:

  • Enforce a 64 character limit for application.id and application.version configuration options.

[6.4.1] - 2022-04-26

Fixed:

  • When using polling mode (stream: false), if the SDK was shut down with close(), a timer task could still remain active for up to 30 seconds (or whatever the polling interval was set to).

[6.4.0] - 2022-03-22

This release is functionally identical to the 6.3.1 release. It exists for compliance with semantic versioning, and to correct the changelog: the new feature described below was accidentally omitted from the changelog, and the minor version number should have been incremented.

Added:

  • LDOptions.application, for configuration of application metadata that may be used in LaunchDarkly analytics or other product features. This does not affect feature flag evaluations.

... (truncated)

Commits

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

@dependabot
Bump semver and launchdarkly-node-server-sdk
5c92fb2 
Bumps [semver](https://github.com/npm/node-semver) to 7.5.3 and updates ancestor dependency [launchdarkly-node-server-sdk](https://github.com/launchdarkly/node-server-sdk). These dependencies need to be updated together.


Updates `semver` from 6.3.0 to 7.5.3
- [Release notes](https://github.com/npm/node-semver/releases)
- [Changelog](https://github.com/npm/node-semver/blob/main/CHANGELOG.md)
- [Commits](npm/node-semver@v6.3.0...v7.5.3)

Updates `launchdarkly-node-server-sdk` from 5.13.4 to 7.0.1
- [Release notes](https://github.com/launchdarkly/node-server-sdk/releases)
- [Changelog](https://github.com/launchdarkly/node-server-sdk/blob/main/CHANGELOG.md)
- [Commits](launchdarkly/node-server-sdk@5.13.4...7.0.1)

---
updated-dependencies:
- dependency-name: semver
  dependency-type: indirect
- dependency-name: launchdarkly-node-server-sdk
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Jun 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants