Update retry to the latest version 🚀

[greenkeeper]

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 0.12.0 of retry was just published.

Dependency	retry
Current Version	0.10.1
Type	dependency

The version 0.12.0 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.

It might be worth looking into these changes and trying to get this project onto the latest version of retry.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.

---

Commits

The new version differs by 17 commits.

• f802d9e Release 0.11.0
• 8dcbf16 Release 0.11.0
• a41d515 Adding npm scripts.
• 8499582 Implement operation.reset(), closes #40.
• 39c9e6f Bind wrapped functions to avoid the hoisting issues that meant the last enumerated original function always getting called (#52)
• 339a30a supports maxRetryTime for retryOperation (#57)
• d2ebfcc Update test script
• 9863ef2 Build please.
• d5157c1 Adding support for a code coverage banner. Fixes #30.
• 9320268 Build please.
• 22ba7e5 Add travis banner integration. Refs #30
• df33062 Clarify order of the errors() function. Fixes #48.
• 4ffe0c5 Make docs on retries more explicit. Fixes #37
• e9fdec1 chore: drop support for Node.js 0.10 (#41)
• 7342e69 Fix typo (#51)

There are 17 commits in total.

See the full diff

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 🌴