search

SenseNet / sn-controls-aurelia

Aurelia controls for sensenet ECM
GNU General Public License v2.0
2 stars 0 forks source link

An in-range update of aurelia-testing is breaking the build 🚨 #81

Closed greenkeeper[bot] closed 5 years ago

greenkeeper[bot] commented 5 years ago

The devDependency aurelia-testing was updated from 1.0.0-beta.4.0.0 to 1.0.0.

🚨 View failing branch.

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

aurelia-testing 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/SenseNet/sn-controls-aurelia/builds/433255185?utm_source=github_status&utm_medium=notification)).
Release Notes for 1.0.0

aurelia-testing 1.0.0

Bug Fixes

  • code example: fix to the manually handling lifecycle example (#82) (b0fb939)
  • waitFor: reject with Error rather than string (#84) (054dab5)
Commits

The new version differs by 8 commits.

  • 90653ca chore(all): prepare release 1.0.0
  • 93d9566 chore(all): prepare release 1.0.0-beta.5.0.0
  • 054dab5 fix(waitFor): reject with Error rather than string (#84)
  • 0635bad doc README.md: fixing formatting (#81)
  • b0fb939 fix(code example): fix to the manually handling lifecycle example (#82)
  • 63d26a1 doc(all): remove unnecessary complex h2s
  • 48a5eaf doc(all): convert metadata to yaml and remove unneeded info
  • 71f2cde doc(all): style and format fixups

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