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

Update deep-eql to the latest version 🚀 #1020

Merged
merged 1 commit into from
Aug 5, 2017

Conversation

greenkeeper[bot]
Copy link
Contributor

@greenkeeper greenkeeper bot commented Aug 5, 2017

Version 3.0.0 of deep-eql just got published.

Dependency deep-eql
Current Version 2.0.2
Type dependency

The version 3.0.0 is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of deep-eql.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.


Release Notes v3.0.0

<a name"3.0.0">

3.0.0 (2017-08-05)

Bug Fixes

  • typo in build script for browserified file (#37) (76963e83)

Breaking Changes

This package no longer supports Node < 4. Please use an older version
of this package if you intend to use Node < 4.
(96ad468e)

Commits

The new version differs by 4 commits.

  • 96ad468 docs: advertise minimum supported node version (#45)
  • 323f3cf perf: improve FakeMap implementation (#41)
  • 1fa5334 docs: document Error comparison rules (#42)
  • 4fba5f1 chore: update type-detect to v4 and remove node 0.12 (#39)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

@greenkeeper greenkeeper bot requested a review from a team as a code owner August 5, 2017 20:43
Copy link
Contributor

@meeber meeber left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

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

Successfully merging this pull request may close these issues.

2 participants