willmendesneto / ng-numbers-only / 78

98%

push

travis-ci

<a href="https://github.com/willmendesneto/ng-numbers-only/commit/5b1d08e1b">Update grunt-contrib-connect to the latest version 🚀 (#18)



## Version **2.0.0** of **grunt-contrib-connect** was just published.

&lt;table&gt;
  &lt;tr&gt;
    &lt;th align=left&gt;
      Dependency
    &lt;/th&gt;
    &lt;td&gt;
      &lt;a target=_blank href=https://github.com/gruntjs/grunt-contrib-connect&gt;grunt-contrib-connect&lt;/a&gt;
    &lt;/td&gt;
  &lt;/tr&gt;
  &lt;tr&gt;
      &lt;th align=left&gt;
       Current Version
      &lt;/th&gt;
      &lt;td&gt;
        1.0.2
      &lt;/td&gt;
    &lt;/tr&gt;
  &lt;tr&gt;
    &lt;th align=left&gt;
      Type
    &lt;/th&gt;
    &lt;td&gt;
      devDependency
    &lt;/td&gt;
  &lt;/tr&gt;
&lt;/table&gt;



The version **2.0.0** is **not covered** by your **current version range**.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of grunt-contrib-connect.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.


---


&lt;details&gt;
&lt;summary&gt;Commits&lt;/summary&gt;
&lt;p&gt;The new version differs by 10 commits.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;https://urls.greenkeeper.io/gruntjs/grunt-contrib-connect/commit/</a><a class="double-link" href="https://github.com/willmendesneto/ng-numbers-only/commit/9da2f3788">9da2f3788</a><a href="https://github.co... (continued)

27 of 29 branches covered (93.1%)

59 of 60 relevant lines covered (98.33%)

8.55 hits per line