search

ljharb / object.assign

ES6 spec-compliant Object.assign shim. From https://github.com/es-shims/es6-shim
https://tc39.es/ecma262/#sec-object.assign
MIT License
107 stars 22 forks source link

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

Closed greenkeeper[bot] closed 7 years ago

greenkeeper[bot] commented 7 years ago

Version 2.8.0 of nsp just got published.

Branch Build failing 🚨
Dependency nsp
Current Version 2.7.0
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 could not complete due to an error [Details](https://travis-ci.org/ljharb/object.assign/builds/272173187?utm_source=github_status&utm_medium=notification)
Commits

The new version differs by 7 commits.

  • 93816b2 2.8.0
  • 6dfcca4 shrinkwrap shuffle apparently
  • 31029c2 Merge pull request #184 from nodesecurity/lock
  • fb48dd1 Merge branch 'master' of github.com:nodesecurity/nsp into lock
  • 82ee301 remove code don't comment it out
  • 1d0b7b5 adding package-lock.json support
  • 56f9848 Fix build status and add mention of nodesecurity.io

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.7.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

ljharb commented 7 years ago

Fixed in 330b9da2570cf4d656e47556641cd8984dba3bce