Skip to content
This repository has been archived by the owner on Sep 30, 2018. It is now read-only.

Update @robotlegsjs/core to the latest version 🚀 #4

Merged
merged 3 commits into from
Aug 30, 2017

Conversation

greenkeeper[bot]
Copy link
Contributor

@greenkeeper greenkeeper bot commented Aug 30, 2017

Version 0.0.4 of @robotlegsjs/core just got published.

Dependency @robotlegsjs/core
Current Version 0.0.3
Type dependency

The version 0.0.4 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 @robotlegsjs/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.


Commits

The new version differs by 8 commits.

  • 9c57bcf update package version to 0.0.4
  • 31602a5 setup npm registry as default
  • ec790f5 chore(package): upgrade yarn.lock file
  • b1fec58 chore(package): update karma to version 1.7.1
  • 2d1787c Merge pull request #5 from RobotlegsJS/greenkeeper-lockfile
  • 41f8326 enable greenkeeper-lockfile
  • 94b674f Merge pull request #4 from RobotlegsJS/upgrade-dependencies
  • d372267 chore(package): update dependencies to latest version

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

@tiagoschenkel tiagoschenkel merged commit 79e288e into master Aug 30, 2017
@tiagoschenkel tiagoschenkel deleted the greenkeeper/@robotlegsjs/core-0.0.4 branch August 30, 2017 20:29
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.

2 participants