search

adarshpastakia / aurelia-ui-framework

A bespoke UI Framework built on Aurelia for desktop business application
https://adarshpastakia.github.io/auf-demo-v4/
MIT License
152 stars 27 forks source link

An in-range update of aurelia-templating is breaking the build 🚨 #215

Open greenkeeper[bot] opened 4 years ago

greenkeeper[bot] commented 4 years ago

The dependency aurelia-templating was updated from 1.10.2 to 1.10.3.

🚨 View failing branch.

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

aurelia-templating 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/adarshpastakia/aurelia-ui-framework/builds/642727674?utm_source=github_status&utm_medium=notification)).
Release Notes for 1.10.3

aurelia-templating 1.10.3

Bug Fixes

  • all: change es2015 back to native-modules (ea50719)
  • ElementEvents: ElementEvents.defaultListenerOptions allows to set default options when subscribing to events (f7e8e32), closes #657
  • shadow-dom: prevent slot leak (#678) (9241dca)
Commits

The new version differs by 8 commits.

  • d75d94f chore(all): add latest build artifacts
  • 6a14247 Merge branch 'develop'
  • 9241dca fix(shadow-dom): prevent slot leak (#678)
  • 20de140 fix(karma): add retainLines to babelPreprocessor
  • ea994d1 fix(typings): fix IStaticResourceConfig typings
  • cff57ef chore(all): add latest build artifacts
  • 879b9c5 Merge branch 'develop'
  • e5d516a chore(all): merge latest release

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

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