search

robototes / robototes-website

Official Robototes team website.
https://www.robototes.com
Other
3 stars 1 forks source link

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

Closed greenkeeper[bot] closed 7 years ago

greenkeeper[bot] commented 7 years ago

Version 2.7.0 of nsp just got published.

Branch Build failing 🚨
Dependency nsp
Current Version 2.6.3
Type devDependency

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:

Status Details - ❌ **continuous-integration/travis-ci/push** The Travis CI build is in progress [Details](https://travis-ci.org/robototes/robototes-website/builds/257946768?utm_source=github_status&utm_medium=notification) - ❌ **semaphoreci** The build failed on Semaphore. [Details](https://semaphoreci.com/robototes/robototes-website/branches/greenkeeper-nsp-2-7-0/builds/1)
Commits

The new version differs by 13 commits.

  • e88fb8a 2.7.0
  • f207e03 fix package.json so things actually work
  • 11d5635 Merge pull request #178 from nodesecurity/quiet-flag
  • cf32c95 remove unused code
  • 5ee23ec Merge pull request #164 from dblandin/devon/update-dockerfile
  • c41e59d Pick Lint
  • a9491bd Add quiet to --output usage
  • 215432f add quiet output
  • c20afb3 drone config
  • d9ba63b Update Dockerfile
  • 73c321d Merge pull request #158 from koresar/patch-1
  • 904dc3e Make sure the table width is a minimum width
  • da2b275 Fix nsp CLI crash in the no window (CI) envs

See the full diff

Not sure how things should work exactly? 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).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 7 years ago

After pinning to 2.6.3 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.