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.

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

An in-range update of lru-memoize is breaking the build 🚨 #142

Open
greenkeeper bot opened this issue Feb 21, 2019 · 1 comment
Open

An in-range update of lru-memoize is breaking the build 🚨 #142

greenkeeper bot opened this issue Feb 21, 2019 · 1 comment

Comments

@greenkeeper
Copy link

greenkeeper bot commented Feb 21, 2019

The dependency lru-memoize was updated from 1.0.2 to 1.1.0.

🚨 View failing branch.

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

lru-memoize 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
  • ci/circleci: build: Your tests failed on CircleCI (Details).

Release Notes for v1.1.0

Bug Fixes

  • Fixed slice/splice typo #88
  • Fix error in IE11 #89

Types

  • Typescript and Flow support! #91
Commits

The new version differs by 9 commits.

  • fab5d61 1.1.0
  • 482226d Added flow types and migrated to jest and rollup (#91)
  • a2313aa fixed linting error
  • 83a9935 v1.0.3
  • 6113106 Upgraded deps
  • bb42316 slice → splice while moving entry to the top (#88)
  • 8ef91af Fix IE11 'findIndex' error (#89)
  • a9b4b3d Merge pull request #86 from dlindenkreuz/typescript-defs
  • 0c5eb9a add typescript type defs

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

@greenkeeper
Copy link
Author

greenkeeper bot commented Feb 21, 2019

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

0 participants