An in-range update of travis-after-all is breaking the build 🚨

[greenkeeper]

Version 1.4.5 of travis-after-all just got published.

Branch	Build failing 🚨
Dependency	travis-after-all
Current Version	1.4.4
Type	devDependency

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

As travis-after-all is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

Commits

The new version differs by 18 commits.

• 9a9aebb Update tests to no longer include Node v5
• 194b09d Update devDependencies
• 29246f2 Fix devDependency Status link from README.md
• 1c2cff4 Clarify section titles in README.md
• 9fa23c9 Fix grammar mistakes in README.md
• 1529531 Update devDependencies
• 15195ee Update tests to also include Node v6
• 8a3d982 Update the list of files to be included by npm
• bd80454 Switch to using SSH keys for GitHub authentication
• eb5b9bb Update tap-mocha-reporter to v0.0.24
• eb6b2e0 Update tap to v5.0.0
• ae72688 Update tap to v3.1.2
• dc5094e Update devDependencies
• da49859 Remove unused glob devDependency
• b5d8b44 Use https:// where possible [ci skip]

There are 18 commits in total.

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 🌴