Skip to content

Conversation

@greenkeeperio-bot
Copy link
Contributor

Hello lovely humans,

babel-core just published its new version 6.18.2.

State Update 🚀
Dependency babel-core
New version 6.18.2
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 babel-core.
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!

🌴


This pull request was created by greenkeeper.io.

Tired of seeing this sponsor message? ⚡ greenkeeper upgrade

@coveralls
Copy link

Coverage Status

Coverage remained the same at 72.0% when pulling 1ad403bfa281b706ed95904d77cb3aa84de12f09 on greenkeeper-babel-core-6.18.2 into a78e8e0 on master.

@nason nason force-pushed the greenkeeper-babel-core-6.18.2 branch from 1ad403b to 522f8fb Compare November 2, 2016 14:13
@coveralls
Copy link

Coverage Status

Coverage remained the same at 72.0% when pulling 522f8fb on greenkeeper-babel-core-6.18.2 into e7af31d on master.

@nason nason merged commit 448b67e into master Nov 2, 2016
@nason nason deleted the greenkeeper-babel-core-6.18.2 branch November 2, 2016 14:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants