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 marko is breaking the build 🚨 #19

Open
greenkeeper bot opened this issue May 23, 2018 · 1 comment
Open

An in-range update of marko is breaking the build 🚨 #19

greenkeeper bot opened this issue May 23, 2018 · 1 comment

Comments

@greenkeeper
Copy link

greenkeeper bot commented May 23, 2018

Version 4.10.0 of marko was just published.

Branch Build failing 🚨
Dependency marko
Current Version 4.9.7
Type dependency

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

marko 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

Commits

The new version differs by 11 commits.

  • d6e251d 4.10.0
  • 6e55f14 Fix #1049 - Fix documentation urls on the website.
  • 5d3e976 Merge pull request #1046 from marko-js/add-failing-tests-from-branches
  • 048a563 Add failing test cases from branches.
  • 7c5089b Merge pull request #1041 from marko-js/on-mount-update-test
  • 1a37333 Add same test for legacy compatibility layer.
  • 5be4d52 Add test for updating in onMount
  • 28ff4e1 fix markdown formatting
  • 6489961 Delete ISSUE_TEMPLATE.md
  • 2433543 Update issue templates
  • 89dfb4b Fixes #877 - Allow array of transformers in marko.json. (#1034)

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
Copy link
Author

greenkeeper bot commented May 23, 2018

After pinning to 4.9.7 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