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 nightmare to the latest version 🚀 #13

Merged
merged 2 commits into from
Mar 2, 2017

Conversation

greenkeeper[bot]
Copy link
Contributor

@greenkeeper greenkeeper bot commented Feb 24, 2017

Version 2.10.0 of nightmare just got published.

Dependency nightmare
Current Version 2.9.1
Type dependency

The version 2.10.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 nightmare.
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.


Commits

The new version differs by 10 commits .

  • e8c4ad3 Release 2.10.0
  • e68d0f2 Merge pull request #992 from itsjustcon/master
  • 24fd158 Merge pull request #1009 from keithkml/patch-1
  • 1c4ca0b Merge pull request #1008 from suniaoo/master
  • 380d01c Remove redundant docs for 'log' event from README
  • 99873d2 changed some var declarations to const
  • e098103 replace the 404 link with valid link
  • 902e30a added Promise override tests
  • 1b0eb67 added docs for new Promise override features
  • a0885fd added ability to override internal Promise library

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 🌴

@coveralls
Copy link

Coverage Status

Coverage remained the same at 61.486% when pulling c9c75d4 on greenkeeper/nightmare-2.10.0 into 8def0f5 on master.

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling b97424e on greenkeeper/nightmare-2.10.0 into ** on master**.

@hfreire hfreire merged commit a76e925 into master Mar 2, 2017
@greenkeeper greenkeeper bot deleted the greenkeeper/nightmare-2.10.0 branch March 2, 2017 19:51
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.

None yet

2 participants