Skip to content

Conversation

@greenkeeper
Copy link
Contributor

@greenkeeper greenkeeper bot commented Feb 13, 2017

Version 1.2.1 of watchpack just got published.

Dependency watchpack
Current Version 1.2.0
Type dependency

The version 1.2.1 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 watchpack.
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 2 commits .

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

coveralls commented Feb 13, 2017

Coverage Status

Coverage remained the same at 100.0% when pulling a3a8a09 on greenkeeper/watchpack-1.2.1 into d37cb13 on master.

@kumar303 kumar303 changed the title Update watchpack to the latest version 🚀 chore: Update watchpack to the latest version 🚀 Feb 13, 2017
@coveralls
Copy link

coveralls commented Feb 13, 2017

Coverage Status

Coverage remained the same at 100.0% when pulling d349e7b on greenkeeper/watchpack-1.2.1 into d053082 on master.

@kumar303 kumar303 merged commit 7a44860 into master Feb 13, 2017
@kumar303 kumar303 deleted the greenkeeper/watchpack-1.2.1 branch February 13, 2017 16:39
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.

4 participants