An in-range update of console-stamp is breaking the build 🚨

[greenkeeper]

The devDependency console-stamp was updated from 0.2.6 to 0.2.7.

🚨 View failing branch.

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

console-stamp 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/appveyor/branch: AppVeyor build failed (Details).

---

Commits

The new version differs by 2 commits.

• aeb14d5 0.2.7
• ab83a19 As of node version 10.0.0 the console.assert implementation is spec compliant and does not throw anymore. We now handle the failing assert and prevent it from do internal calls to warn. This fixes #29

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

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

[greenkeeper]

• The devDependency console-stamp was updated from 0.2.7 to 0.2.8.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 5 commits.

• 48b5441 0.2.8
• 088b602 Prepare for 3.0.0 release
• 53f9233 Merge pull request #32 from starak/0.2.8
• fa94a16 Prepare for 3.0.0 release
• 19d843a CircleCI...

See the full diff

[greenkeeper]

• The devDependency console-stamp was updated from 0.2.8 to 0.2.9.

Your tests are still failing with this version. Compare changes