An in-range update of can-define is breaking the build 🚨

[greenkeeper[bot]]

The dependency can-define was updated from 2.7.18 to 2.7.19.

🚨 View failing branch.

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

can-define 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 failed ([Details](https://travis-ci.org/canjs/bit-docs-html-canjs/builds/557579443?utm_source=github_status&utm_medium=notification)).

---

Release Notes for Zero-argument getter warning updates

This release fixes two issues - It warns when you have type or Type with a zero argument getter and also fixes Default to warn even when the the default value is falsey (previously it only warned when default had non-falsey values)

Commits

The new version differs by 4 commits.

• f9e3d05 2.7.19
• 63a2630 465 warn for getter with type and 466 default with falsey value (#467)
• a68859a Merge pull request #464 from canjs/landscaper/travis
• 482e5c8 Migrate to xenial in travis

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]]

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

[greenkeeper[bot]]

• The dependency can-define was updated from 2.7.19 to 2.7.20.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Commits

The new version differs by 2 commits.

• 43a3ab3 2.7.20
• 9a35ef9 468 remove false warning if only default type (#469)

See the full diff