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

chore(greenkeeper): Update async #14

Merged
merged 2 commits into from
May 27, 2019
Merged

Conversation

greenkeeper[bot]
Copy link

@greenkeeper greenkeeper bot commented May 26, 2019

The dependency async was updated from 2.6.2 to 3.0.1.

This version is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.


Find out more about this release.

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 🌴

@coveralls
Copy link

coveralls commented May 26, 2019

Pull Request Test Coverage Report for Build 112

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 97.257%

Totals Coverage Status
Change from base Build 105: 0.0%
Covered Lines: 494
Relevant Lines: 503

💛 - Coveralls

@randytarampi randytarampi added this to In Progress in lwip via automation May 27, 2019
@randytarampi randytarampi merged commit 105b380 into master May 27, 2019
lwip automation moved this from In Progress to Done May 27, 2019
@randytarampi randytarampi deleted the greenkeeper/async-3.0.1 branch May 27, 2019 05:42
@randytarampi
Copy link
Owner

🎉 This PR is included in version 1.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

Successfully merging this pull request may close these issues.

None yet

2 participants