Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update eslint-config-dustinspecker to version 0.4.1 🚀 #23

Conversation

greenkeeperio-bot
Copy link
Contributor

Hello 👋

🚀🚀🚀

eslint-config-dustinspecker just published its new version 0.4.1, which is not covered by your current version range.

If this pull request passes your tests you can publish your software with the latest version of eslint-config-dustinspecker – otherwise use this branch to work on adaptions and fixes.

Happy fixing and merging 🌴


The new version differs by 11 commits .

  • d68cbad chore(release): bump version to 0.4.1
  • 12dec0d feat(all): disable consistent returng
  • 8750487 Merge pull request #20 from dustinspecker/greenkeeper-ava-0.12.0
  • 07182eb chore(package): update ava to version 0.12.0
  • 4ac4751 chore(release): bump version to 0.4.0
  • 23e4ffe Merge pull request #19 from dustinspecker/greenkeeper-eslint-2.0.0
  • 34db3ed chore(package): update eslint to version 2.0.0
  • deb13e9 Merge pull request #18 from dustinspecker/greenkeeper-ava-0.11.0
  • 720d770 chore(package): update ava to version 0.11.0
  • a7493f0 Merge pull request #17 from dustinspecker/greenkeeper-ava-0.10.0
  • 907e649 chore(package): update ava to version 0.10.0

See the full diff.


This pull request was created by greenkeeper.io.
It keeps your software, up to date, all the time.

Tired of seeing this sponsor message? Upgrade to the supporter plan! You'll also get your pull requests faster ⚡

@dustinspecker dustinspecker deleted the greenkeeper-eslint-config-dustinspecker-0.4.1 branch February 23, 2016 23:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants