search

zotoio / github-task-manager

receive github hook, notify agent, receive task results, notify github
MIT License
12 stars 4 forks source link

An in-range update of ldclient-node is breaking the build 🚨 #145

Open greenkeeper[bot] opened 6 years ago

greenkeeper[bot] commented 6 years ago

The dependency ldclient-node was updated from 5.4.2 to 5.5.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

ldclient-node is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details - ❌ **continuous-integration/travis-ci/push:** The Travis CI build could not complete due to an error ([Details](https://travis-ci.org/zotoio/github-task-manager/builds/438836186?utm_source=github_status&utm_medium=notification)).
Release Notes for 5.5.0

[5.5.0] - 2018-10-08

Added:

  • The allFlagsState method now accepts a new option, detailsOnlyForTrackedFlags, which reduces the size of the JSON representation of the flag state by omitting some metadata. Specifically, it omits any data that is normally used for generating detailed evaluation events if a flag does not have event tracking or debugging turned on.

Fixed:

  • Fixed an error that would occur in two cases where the client should return a default value: evaluating a flag when the client and the feature store are not yet initialized, and evaluating with no flag key. (Thanks, SharkofMirkwood!)
  • JSON data from allFlagsState is now slightly smaller even if you do not use the new option described above, because it completely omits the flag property for event tracking unless that property is true.
Commits

The new version differs by 3 commits.

  • 6a47a4a Update Changelog for release of version 5.5.0
  • d273e60 prepare 5.5.0 release (#124)
  • a4dc34f Fix uncaught 'variationErr is not defined' exception (#123)

See the full diff

FAQ and help There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 6 years ago

After pinning to 5.4.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

greenkeeper[bot] commented 5 years ago

Your tests are still failing with this version. Compare changes

Release Notes for 5.6.0

[5.6.0] - 2018-11-14

Added:

  • To make it easier to build feature store integrations for databases other than Redis, some of the feature store support logic has been made into a reusable component in caching_store_wrapper.js.

Changed:

  • For proxy support, the SDK now uses the published version of the tunnel package from NPM, rather than a Git reference to a fork.
Commits

The new version differs by 3 commits.

  • 28a383d Update Changelog for release of version 5.6.0
  • 5242ab9 prepare 5.6.0 release (#128)
  • 7bacfe2 Preparing for release of version 5.5.0

See the full diff

greenkeeper[bot] commented 5 years ago

Your tests are still failing with this version. Compare changes

Release Notes for 5.6.1

[5.6.1] - 2018-11-15

Fixed:

  • Fixed a bug introduced in v5.6.0 that could cause an unhandled promise rejection if a Redis error occurred while trying to query all flags from Redis.
  • Fixed a bug introduced in v5.6.0 that could cause an exception when calling close() on a client that was using a Redis feature store without in-memory caching.
Commits

The new version differs by 3 commits.

  • 2c1af6c Update Changelog for release of version 5.6.1
  • 500e3a5 prepare 5.6.1 release (#129)
  • 460619a Preparing for release of version 5.6.0

See the full diff

greenkeeper[bot] commented 5 years ago

Your tests are still failing with this version. Compare changes

Release Notes for 5.6.2

[5.6.2] - 2018-11-15

Fixed:

  • Creating multiple clients with the default in-memory feature store (i.e. leaving config.featureStore unset) was causing all of the clients to share the same feature store instance. This has been fixed so they will now each get their own in-memory store. (Thanks, seanparmelee!)
Commits

The new version differs by 4 commits.

  • 891752e Update Changelog for release of version 5.6.2
  • 0e734d9 Merge pull request #130 from seanparmelee/separate-feature-store
  • 6bc2fc4 ensure the default config does not share the featureStore
  • ab776b1 Preparing for release of version 5.6.1

See the full diff

greenkeeper[bot] commented 5 years ago

Your tests are still failing with this version. Compare changes

Release Notes for 5.7.0

[5.7.0] - 2019-01-11

Added:

Fixed:

  • Fixed a potential race condition that could happen when using a DynamoDB or Consul feature store. The Redis feature store was not affected.
Commits

The new version differs by 3 commits.

  • 5da8846 Update Changelog for release of version 5.7.0
  • d7a95a4 prepare 5.7.0 release (#134)
  • 1273ba9 Preparing for release of version 5.6.2

See the full diff

greenkeeper[bot] commented 5 years ago

Your tests are still failing with this version. Compare changes

Release Notes for 5.7.1

[5.7.1] - 2019-01-16

Changes are only in test code used by other libraries. There is no need to upgrade to this release.

Commits

The new version differs by 3 commits.

  • 50c37b3 Update Changelog for release of version 5.7.1
  • 368e348 prepare 5.7.1 release (#135)
  • 5d43940 Preparing for release of version 5.7.0

See the full diff

greenkeeper[bot] commented 5 years ago

Your tests are still failing with this version. Compare changes

Release Notes for 5.7.2

[5.7.2] - 2019-02-22

Fixed:

  • Calling identify() or track() with no user object, or with a user that has no key, will now cause the SDK to log a warning (as the other SDKs do). The SDK no longer sends an analytics event in this case, since LaunchDarkly would discard the event as invalid anyway. Also, previously, calling identify() with no user object would throw an exception.
  • FileDataSource, in auto-update mode, could sometimes reload files more than once when they were only modified once (due to a known issue with Node's fs.watch). This should no longer happen. (#138)
  • Fixed dependency vulnerabilities flagged by npm audit. These were all for test-only dependencies, so would not affect production code.
  • Previously, CI tests were only running on Linux. We have added a CI test suite that runs on Windows, using the latest stable version of Node.
  • A supported user property, privateAttributeNames, was not usable from TypeScript because it was omitted from the TypeScript declarations.
  • In TypeScript, asynchronous methods that can either take a callback or return a Promise were not usable in the Promise style, because the return types were declared incorrectly. (#141)
  • Some TypeScript declarations that used type now use interface instead, except for LDFlagValue which is a type alias. This should not affect regular usage of the SDK in TypeScript, but it is easier to extend an interface than a type if desired.
Commits

The new version differs by 3 commits.

  • 06709c2 Update Changelog for release of version 5.7.2
  • e626445 5.7.2 (#142)
  • 3ea1039 Preparing for release of version 5.7.1

See the full diff

greenkeeper[bot] commented 5 years ago

Your tests are still failing with this version. Compare changes

Release Notes for 5.7.3

[5.7.3] - 2019-03-21

Changed:

  • The default value for the configuration property capacity (maximum number of events that can be stored at once) is now 10000, consistent with the other SDKs, rather than 1000.

Fixed:

  • A missing var keyword could cause an error in strict mode when evaluating a flag with rollouts. (Thanks, phillipb!)
  • The user attribute secondary was not included in the TypeScript declarations and therefore could not be used from TypeScript code.
Commits

The new version differs by 5 commits.

  • 1d004f4 Update Changelog for release of version 5.7.3
  • 771bb99 prepare 5.7.3 release (#146)
  • 3cc345c Properly define the variable. (#145)
  • 1a93e53 Update issue templates
  • 3f7728c Preparing for release of version 5.7.2

See the full diff

greenkeeper[bot] commented 5 years ago

Your tests are still failing with this version. Compare changes

Release Notes for 5.7.4

[5.7.4] - 2019-04-02

Fixed:

  • Setting user attributes to non-string values when a string was expected would cause analytics events not to be processed. The SDK will now convert attribute values to strings as needed. (#147)
  • If track or identify is called without a user, the SDK now logs a warning, and does not send an analytics event to LaunchDarkly (since it would not be processed without a user).
Commits

The new version differs by 3 commits.

  • 1b5c078 Update Changelog for release of version 5.7.4
  • 8bf8808 prepare 5.7.4 release (#148)
  • 89bbd31 Preparing for release of version 5.7.3

See the full diff

greenkeeper[bot] commented 5 years ago

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 2 commits.

  • 4a0f51c prepare 5.8.0 release (#149)
  • 566dea0 Preparing for release of version 5.7.4

See the full diff