Skip to content

babel-eslint@6.1.1 untested ⚠️#12

Merged
madhums merged 1 commit into
masterfrom
greenkeeper-babel-eslint-6.1.1
Jul 9, 2016
Merged

babel-eslint@6.1.1 untested ⚠️#12
madhums merged 1 commit into
masterfrom
greenkeeper-babel-eslint-6.1.1

Conversation

@greenkeeperio-bot
Copy link
Copy Markdown
Contributor

Hello lovely humans,

babel-eslint just published its new version 6.1.1.

State No tests ⚠️
Dependency babel-eslint
New version 6.1.1
Type devDependency

This version is covered by your current version range, but I could not detect automated tests for this project. Without a test suite I can not really tell whether your project still works.

I was looking at the latest commit of your default branch, but GitHub said there is no status attached to it.

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 5 commits .

  • 36a6a6d 6.1.1
  • 254e6ea Create a variable for class properties in scope instead of deleting the key (#336)
  • 2d72002 remove hardcoded strict mode value (#331)
  • c7efe11 Add testcase for space-comment and shebang #163
  • 40cb21c Testcase for newline-before-return shouldn't fail with comments. (#300)

See the full diff.


This pull request was created by greenkeeper.io.

Tired of seeing this sponsor message? ⚡ greenkeeper upgrade

@madhums madhums force-pushed the greenkeeper-babel-eslint-6.1.1 branch from 417c33d to 544fcaf Compare July 9, 2016 21:11
@madhums madhums merged commit d816aaa into master Jul 9, 2016
@madhums madhums deleted the greenkeeper-babel-eslint-6.1.1 branch July 9, 2016 21:11
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.

2 participants