An in-range update of nsp is breaking the build 🚨


## Version **2.7.0** of [nsp](https://github.com/nodesecurity/nsp) just got published.

<table>
  <tr>
    <th align=left>
      Branch
    </th>
    <td>
      <a href="/gregswindle/eslint-plugin-swagger/compare/greenkeeper%2Fnsp-2.7.0">Build failing 🚨</a>
    </td>
  </tr>
  <tr>
    <th align=left>
      Dependency
    </td>
    <td>
      nsp
    </td>
  </tr>
  <tr>
    <th align=left>
      Current Version
    </td>
    <td>
      2.6.3
    </td>
  </tr>
  <tr>
    <th align=left>
      Type
    </td>
    <td>
      devDependency
    </td>
  </tr>
</table>

This version is **covered** by your **current version range** and after updating it in your project **the build failed**.


As nsp is “only” a devDependency of this project it **might not break production or downstream projects**, but “only” your build or test tools – **preventing new deploys or publishes**.

I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:



<details>
<summary>Status Details</summary>

- ❌ **bitHound - Dependencies** 1 failing dependency. [Details](https://www.bithound.io/github/gregswindle/eslint-plugin-swagger/ee1b9c4f223f2b52ca3fae93aaf7f09df3c93d90/dependencies/npm#filter-failing-dep)
- ✅ **bitHound - Code** No failing files. [Details](https://www.bithound.io/github/gregswindle/eslint-plugin-swagger/ee1b9c4f223f2b52ca3fae93aaf7f09df3c93d90/files?status=passing)
- ✅ **continuous-integration/travis-ci/push** The Travis CI build passed [Details](https://travis-ci.org/gregswindle/eslint-plugin-swagger/builds/257947429?utm_source=github_status&utm_medium=notification)
- ✅ **coverage/coveralls** First build on greenkeeper/nsp-2.7.0 at 100.0% [Details](https://coveralls.io/builds/12568652)
</details>


---

<details>
<summary>Commits</summary>
<p>The new version differs by 13 commits.</p>
<ul>
<li><a href="https://urls.greenkeeper.io/nodesecurity/nsp/commit/e88fb8a7bc7cdca088702c31b3b716a92f4fce3c"><code>e88fb8a</code></a> <code>2.7.0</code></li>
<li><a href="https://urls.greenkeeper.io/nodesecurity/nsp/commit/f207e0339ca028fecdee0f87950d0026b4a96bc9"><code>f207e03</code></a> <code>fix package.json so things actually work</code></li>
<li><a href="https://urls.greenkeeper.io/nodesecurity/nsp/commit/11d5635385cdb453f1201b2dec0898f0780d4838"><code>11d5635</code></a> <code>Merge pull request #178 from nodesecurity/quiet-flag</code></li>
<li><a href="https://urls.greenkeeper.io/nodesecurity/nsp/commit/cf32c959d6d4b2690822aea1ebed9b3589294ad9"><code>cf32c95</code></a> <code>remove unused code</code></li>
<li><a href="https://urls.greenkeeper.io/nodesecurity/nsp/commit/5ee23ec381666a3842eeb5f8546dc459a603e6b4"><code>5ee23ec</code></a> <code>Merge pull request #164 from dblandin/devon/update-dockerfile</code></li>
<li><a href="https://urls.greenkeeper.io/nodesecurity/nsp/commit/c41e59debc0c186154ea9b58cb0e28a83d02f681"><code>c41e59d</code></a> <code>Pick Lint</code></li>
<li><a href="https://urls.greenkeeper.io/nodesecurity/nsp/commit/a9491bdeaab7a34f81c1a720bde70a09625294ca"><code>a9491bd</code></a> <code>Add quiet to --output usage</code></li>
<li><a href="https://urls.greenkeeper.io/nodesecurity/nsp/commit/215432fccd7bd2a02de50fa6533a4be6c6957871"><code>215432f</code></a> <code>add quiet output</code></li>
<li><a href="https://urls.greenkeeper.io/nodesecurity/nsp/commit/c20afb353bdf243c0824818c9018c50a1c33884a"><code>c20afb3</code></a> <code>drone config</code></li>
<li><a href="https://urls.greenkeeper.io/nodesecurity/nsp/commit/d9ba63ba4c842114f6e76024214f3017ce6f3936"><code>d9ba63b</code></a> <code>Update Dockerfile</code></li>
<li><a href="https://urls.greenkeeper.io/nodesecurity/nsp/commit/73c321d171d59eb037553fa31cf5ad6bdf092063"><code>73c321d</code></a> <code>Merge pull request #158 from koresar/patch-1</code></li>
<li><a href="https://urls.greenkeeper.io/nodesecurity/nsp/commit/904dc3ee6a3c25a038cbf4454eef6dac97850b14"><code>904dc3e</code></a> <code>Make sure the table width is a minimum width</code></li>
<li><a href="https://urls.greenkeeper.io/nodesecurity/nsp/commit/da2b275ff7cf449430073a0e848617612edb6a64"><code>da2b275</code></a> <code>Fix nsp CLI crash in the no window (CI) envs</code></li>
</ul>
<p>See the <a href="https://urls.greenkeeper.io/nodesecurity/nsp/compare/ee544f5fac4899cc6b1f81f123c39c293e4bf01b...e88fb8a7bc7cdca088702c31b3b716a92f4fce3c">full diff</a></p>
</details>


<details>
<summary>Not sure how things should work exactly?</summary>

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).
</details>


---


Your [Greenkeeper](https://greenkeeper.io) Bot :palm_tree:


Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

An in-range update of nsp is breaking the build 🚨 #25

Version 2.7.0 of nsp just got published.

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Branch	Build failing 🚨
Dependency	nsp
Current Version	2.6.3
Type	devDependency

An in-range update of nsp is breaking the build 🚨 #25

Description

Version 2.7.0 of nsp just got published.

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions