uPortal-Attic / uportal-app-framework

Framework for creating uPortal Applications
http://uportal-project.github.io/uportal-app-framework/
Apache License 2.0
23 stars 31 forks source link

An in-range update of superstatic is breaking the build 🚨 #841

Closed greenkeeper[bot] closed 6 years ago

greenkeeper[bot] commented 6 years ago

The devDependency superstatic was updated from 6.0.2 to 6.0.3.

🚨 View failing branch.

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

superstatic is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details - ❌ **continuous-integration/travis-ci/push:** The Travis CI build could not complete due to an error ([Details](https://travis-ci.org/uPortal-Project/uportal-app-framework/builds/434360934?utm_source=github_status&utm_medium=notification)).

Release Notes for v6.0.3
  • removed nsp from dev dependencies
  • dependency updates to fix audit issues
Commits

The new version differs by 7 commits.

  • 16c7cb9 [firebase-release] Updated Superstatic to 6.0.3
  • a582e41 update changelog for my changes (#265)
  • a19a6d2 Travis Update, Removing nsp (#264)
  • 69705d9 Merge pull request #263 from firebase/bk-update-notifier
  • bf37c3d updating update-notifier
  • aca4f96 updating some test deps
  • 7820336 [firebase-release] Removed change log and reset repo after 6.0.2 release

See the full diff

FAQ and help There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 6 years ago

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

ChristianMurphy commented 6 years ago

Issue appears to be with package-lock.json being out of sync with package.json