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 standard.
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.
Coverage remained the same at 100.0% when pulling 836a6eeac2ced0b22838a0ce9d6a0cbe7af7cdf6 on greenkeeper-standard-8.2.0 into dc4aac145b9bff41ebc7b105e0fc34b2b390fec2 on master.
Coverage remained the same at 100.0% when pulling 836a6eeac2ced0b22838a0ce9d6a0cbe7af7cdf6 on greenkeeper-standard-8.2.0 into dc4aac145b9bff41ebc7b105e0fc34b2b390fec2 on master.
Coverage remained the same at 100.0% when pulling ecc6317a20ae96c7223ab580cc7da91153b4b1d3 on greenkeeper-standard-8.2.0 into eb491d312d2b0653fcfd76af7c582208b36eab4c on master.
Coverage remained the same at 100.0% when pulling ecc6317a20ae96c7223ab580cc7da91153b4b1d3 on greenkeeper-standard-8.2.0 into eb491d312d2b0653fcfd76af7c582208b36eab4c on master.
Coverage remained the same at 100.0% when pulling ecc6317a20ae96c7223ab580cc7da91153b4b1d3 on greenkeeper-standard-8.2.0 into eb491d312d2b0653fcfd76af7c582208b36eab4c on master.
Hello lovely humans,
standard just published its new version 8.2.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 standard. 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 98 commits .
a8b2f78
authors
95b5f09
8.2.0
bdcad43
changelog
94b0e7f
code>eslint-config-standard-jsx@3.1.0</code00bda98
code>eslint-config-standard@6.0.1</codec633efe
Merge pull request #638 from feross/lu-patch-1
45c026b
code>eslint@~3.6.0</code2e2847a
AUTHORS
4e0667d
8.1.0
3c9ac4f
changelog
f99d5bb
Merge pull request #627 from feross/update-deps
0879f41
code>eslint@~3.5.0</code8a9b75e
code>eslint-config-standard-jsx@3.0.1</codef4407e3
code>eslint-config-standard@6.0.1</code8cd51d9
Merge pull request #624 from feross/timoxley-patch-1
There are 98 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade