An in-range update of aurelia-validation is breaking the build 🚨

[greenkeeper]

The dependency aurelia-validation was updated from 1.5.0 to 1.6.0.

🚨 View failing branch.

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

aurelia-validation 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).

---

Release Notes for 1.6.0

aurelia-validation 1.6.0

Bug Fixes

• all: update binding library and fix TS errors (33c91a1)
• ExpressionVisitor: not redeclare imports (15109b3), closes #537

Features

• config: make config constructor param optional and place default trigger in static property (a52f4c4)
• config: make the setters chainable (bd118a6)
• config: rename global config class (c4e5fe2)
• config: support global config option for default validation trigger (39a4e67)

Commits

The new version differs by 15 commits.

• d45fe85 chore(release): 1.6.0
• b47cbf5 chore(all): prepare release
• 44cc13b Merge pull request #541 from bigopon/master
• 75086a3 chore(build): fix build path
• 463aafc Merge pull request #540 from bigopon/master
• d64419e chore(build): fix tests
• c608074 Merge pull request #539 from bigopon/master
• 8fedbe2 chore(build): update deps/rollup ts, fix build
• 33c91a1 fix(all): update binding library and fix TS errors
• 15109b3 fix(ExpressionVisitor): not redeclare imports
• 5b09f86 Merge pull request #536 from RomkeVdMeulen/feat-535-configure-trigger
• bd118a6 feat(config): make the setters chainable
• c4e5fe2 feat(config): rename global config class
• a52f4c4 feat(config): make config constructor param optional and place default trigger in static property
• 39a4e67 feat(config): support global config option for default validation trigger

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