enqueuer-land/stacker

An in-range update of vue is breaking the build 🚨

greenkeeper opened this issue Β· 1 comments

There have been updates to the vue monorepo:

    • The dependency vue was updated from 2.6.7 to 2.6.8.

🚨 View failing branch.

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

This monorepo update includes releases of one or more dependencies which all belong to the vue group definition.

vue 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).

Release Notes for v2.6.8

Bug Fixes

Commits

The new version differs by 15 commits.

  • d123c7e build: release 2.6.8
  • 869a819 build: build 2.6.8
  • 372d71c docs: clarify docs about using template compiler (#9508)
  • cbad54a fix(compiler): set end location for incomplete elements (#9598)
  • 1574ade test: Add a unit test for "$off event and this event added by $once" (#9550)
  • 38825ff test: add a test case for ssr max stack size limit
  • 571a488 fix: further adjust max stack size
  • 03c13de refactor: remove unncessary condition
  • ed34113 fix: handle async component when parent is toggled before resolve (#9572)
  • 241eea1 fix(types): allow scoped slots to return a single VNode (#9563)
  • f333016 fix(types): update this for nextTick api (#9541)
  • 2277b23 fix: scoped slots dynamic check should include v-for on element itself
  • 7912f75 fix: avoid compression of unicode sequences by using regexps (#9595)
  • 060c3b9 fix: fix modifier parsing for dynamic argument with deep path (#9585)
  • 2ec5b64 chore: update sponsors [ci skip] (#9588)

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 🌴

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