🚨🔥⚠️ Action required: Switch to the new Greenkeeper now! 🚨🔥⚠️
This version of Greenkeper will be shutdown on May 31st.
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
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 eslint-plugin-import.
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 :sparkles:
You rock!
:palm_tree:
The new version differs by 443 commits .
b79e083Merge pull request #837 from benmosher/release-2.3.0
Hello lovely humans,
eslint-plugin-import just published its new version 2.3.0.
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 eslint-plugin-import. 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 :sparkles:
You rock!
:palm_tree:
The new version differs by 443 commits .
b79e083Merge pull request #837 from benmosher/release-2.3.074425a2changelog update for 2.3.01377f55bump v2.3.02efc41afix null pointer exception (#717) (#797)0fb592eAdd support to specify the package.json (#685)2cc9768Add test for flow type export (#835)bd0e5e3Merge pull request #821 from smably/patch-1412e518Clarify docs for glob arrays106740fchore(package): update typescript-eslint-parser to version 2.1.0 (#790)6288cf9chore(package): update babel-register to version 6.24.1 (#796)2e9eea6newline-after-import test syntax failsc9f10e8extensions test fixes, attempt 2861765ffix babel syntax errors in extensions tests82f796cchore(package): update cross-env to version 4.0.0 (#783)98e7048Merge pull request #757 from gmathieu/fix-default-keywordThere are 250 commits in total. See the full diff.