Skip to content
This repository has been archived by the owner on Dec 19, 2017. It is now read-only.

Update es6-promise to version 4.0.0 πŸš€ #103

Closed
wants to merge 1 commit into from

Conversation

greenkeeperio-bot
Copy link
Contributor

Hello lovely humans,

es6-promise just published its new version 4.0.0.

State Update πŸš€
Dependency es6-promise
New version 4.0.0
Type devDependency

This version 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 es6-promise.
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.

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!

🌴


The new version differs by 134 commits .

There are 134 commits in total. See the full diff.


This pull request was created by greenkeeper.io.

Tired of seeing this sponsor message? ⚑ greenkeeper upgrade

@coveralls
Copy link

coveralls commented Sep 27, 2016

Coverage Status

Coverage remained the same at 93.556% when pulling 812b838 on greenkeeper-es6-promise-4.0.0 into 3f871f5 on master.

@caseyWebb caseyWebb closed this Sep 27, 2016
@caseyWebb caseyWebb deleted the greenkeeper-es6-promise-4.0.0 branch September 27, 2016 13:13
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants