search

WFCD / warframe-hub

:blue_book: Warframe hub strives to be the community center of the Warframe game
https://hub.warframestat.us
Apache License 2.0
82 stars 28 forks source link

An in-range update of hbs is breaking the build 🚨 #261

Closed greenkeeper[bot] closed 5 years ago

greenkeeper[bot] commented 5 years ago

The dependency hbs was updated from 4.0.2 to 4.0.3.

🚨 View failing branch.

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

hbs is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details - ❌ **continuous-integration/travis-ci/push:** The Travis CI build could not complete due to an error ([Details](https://travis-ci.org/WFCD/warframe-hub/builds/500453290?utm_source=github_status&utm_medium=notification)).
Commits

The new version differs by 21 commits ahead by 21, behind by 2.

  • 5d71299 v4.0.3
  • 05ca647 tests: add app.render tests
  • a2caf93 build: remove unused git submodule
  • 3aeced2 Fix path for partials multiple dirs deep on Windows
  • aaaa876 docs: update links in readme
  • 4a24e57 build: add Windows CI with AppVeyor
  • 2523a47 build: support Node.js 10.x
  • 119cf87 build: support Node.js 8.x
  • 4b21576 build: pin Node.js versions to minor
  • 7a18a89 docs: add history back to 2.0.0
  • f270c6c tests: use supertest for http assertions
  • effe41c tests: fix express 3.x tests not reporting
  • ea17cb5 tests: use system npm to install express
  • bb30585 build: add coverage reporting
  • 75d92fc docs: use standard badge layout

There are 21 commits in total.

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 5 years ago

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