Skip to content
This repository was archived by the owner on Nov 27, 2023. It is now read-only.

Conversation

@greenkeeperio-bot
Copy link
Contributor

Hello lovely humans,

babylon just published its new version 6.11.3.

State Update 🚀
Dependency babylon
New version 6.11.3
Type dependency

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 babylon.
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 8 commits .

  • 45c68c7 6.11.3
  • 4847403 add npm run changelog
  • 7877829 Add static errors for object rest (#149)
  • 9cc0981 get / set are valid property names in default assignment (#142)
  • 4115bcb Fix travis
  • 44d44a2 changelog update
  • a1c0ef2 Don't build on *.md change [skip ci]
  • 6ce192d 6.11.2 changelog [skip ci]

See the full diff.


This pull request was created by greenkeeper.io.

Tired of seeing this sponsor message? ⚡ greenkeeper upgrade

@KnisterPeter KnisterPeter force-pushed the greenkeeper-babylon-6.11.3 branch from 0d0e904 to c6f0805 Compare October 1, 2016 21:54
@KnisterPeter KnisterPeter merged commit 36f9701 into master Oct 1, 2016
@KnisterPeter KnisterPeter deleted the greenkeeper-babylon-6.11.3 branch October 1, 2016 22:01
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.

3 participants