Hello lovely humans,

typings just published its new version 2.1.0.

This version is covered by your current version range and after updating it in your project the build went from success to failure.

As typings 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 💪

Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project ✨

You rock!

🌴

GitHub Release

Changed

• Use global promises over any-promise
• Updated documentation

The new version differs by 8 commits .

• afc99a2 v2.1.0
• fed00bf Update generated documentation
• 454fd1f Update bin-install.ts (#744)
• ebecc13 Update README.md (#742)
• c67bd61 Update build to use native promises
• 23e4906 Document supported node versions in FAQ (#737)
• e42ec68 Update TSLint
• 68c9af7 chore(package): update tslint-config-standard to version 2.0.0 (#731)

See the full diff.

This pull request was created by greenkeeper.io.

_{Tired of seeing this sponsor message? ⚡ greenkeeper upgrade}