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 87.302% when pulling 2cf52d99e70c0f3e5b3d8e2329512c1062badbc2 on greenkeeper-standard-8.4.0 into 81beba4f723f2009695e29508211752460e6d1f1 on master.
Coverage remained the same at 87.302% when pulling fc60988342c099007c0b86ba00fd928bb537f6ae on greenkeeper-standard-8.4.0 into 0429f86ae4ac0539b26a3719c8987c4be6f9a158 on master.
Coverage remained the same at 87.302% when pulling a4a92adb1f88cd6cb3f058becf03f0fa3831f449 on greenkeeper-standard-8.4.0 into 20fea19687014cf05c7658bd1701894f4194cc55 on master.
Coverage remained the same at 87.302% when pulling 9dd20e2f315245e96559bdb39562ea7c02c4771b on greenkeeper-standard-8.4.0 into 28e358a07270ef3de3c3b31529aa86f786335815 on master.
Hello lovely humans,
standard just published its new version 8.4.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 14 commits .
76d4e9d
authors
bc05f8b
8.4.0
4aad40c
Merge pull request #656 from feross/feross/deps
73e2650
8.4.0 changelog
09ca0a5
Merge pull request #655 from feross/feross/654
c0a4af5
code>eslint-plugin-promise@~3.0.0</code9e1291c
Update ESLint to 3.7.x
99a1d90
Dependencies: Use ~ instead of ^.
92743f4
Merge pull request #651 from feross/feross/webstorm
a33cf31
Webstorm instructions should reference eslint-config-standard-jsx
12e3bef
Fixes for PR #644
d962c0f
Merge pull request #644 from chenxsan/update-vscode-formatter
d657d05
update text
ab30aed
update vscode editor extension
See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade