Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

An in-range update of vue-template-compiler is breaking the build 🚨 #37

Open
greenkeeper bot opened this issue Jul 21, 2017 · 1 comment
Open

Comments

@greenkeeper
Copy link

greenkeeper bot commented Jul 21, 2017

Version 2.4.2 of vue-template-compiler just got published.

Branch Build failing 🚨
Dependency vue-template-compiler
Current Version 2.4.1
Type devDependency

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

As vue-template-compiler is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v2.4.2

Bug Fixes

  • v-on: revert component root data.on/data.nativeOn behavior for 1713061, closes #6109
  • checkbox v-model="array" ignore false-value (#6180) 3d14e85, closes #6178
  • compile: properly generate comments with special character (#6156) d03fa26, closes #6150
  • parser: only ignore the first newline in <pre> 082fc39, closes #6146
  • provide/inject: merge provide properly from mixins 3036551, closes #6175
  • provide/inject: resolve inject properly from mixins (#6107) b0f00e3, closes #6093
  • transition: should trigger transition hooks for v-show in ie9 9b4dbba, closes #5525
  • v-bind: respect .prop modifier on components (#6159) 06b9b0b
  • v-model: use stricter check for <select> option update c70addf, closes #6112
  • ensure looseEqual is not dependant on key enumeration order a8ac129, closes #5908
  • include boolean in isPrimitive check (#6127) be3dc9c, closes #6126
  • work around IE/Edge bug when accessing document.activeElement from iframe fc3d7cd, closes #6157

Improvements

  • warn when assigning to computed property with no setter eb9168c, closes #6078

Reverts

  • perf: remove src directory from npm module (#6072) ec4b1be
Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

@greenkeeper
Copy link
Author

greenkeeper bot commented Jul 21, 2017

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

0 participants