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 mustache is breaking the build 🚨 #261

Open
greenkeeper bot opened this issue Aug 7, 2018 · 1 comment
Open

An in-range update of mustache is breaking the build 🚨 #261

greenkeeper bot opened this issue Aug 7, 2018 · 1 comment

Comments

@greenkeeper
Copy link

greenkeeper bot commented Aug 7, 2018

Version 2.3.1 of mustache was just published.

Branch Build failing 🚨
Dependency mustache
Current Version 2.3.0
Type dependency

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

mustache 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.

  • 9e8035d :ship: bump to version 2.3.1
  • 2659301 Fix Rakefile by deleting refs to removed install tasks
  • e443ada Use ngrok rather than localtunnel when running browser tests (#668)
  • 5bbe25e Fix browser test suite by using Node.js 6 (#667)
  • 0a9999a Install release tools with npm rather than via pre-commit hook (#666)
  • 28ca619 fix bug: cache actually not working (#664)
  • 85a2c2d Readme: Mustache.parse returns an array of Tokens (#657)
  • 3fddfb1 Document global Mustache.escape overriding capacity (#644)
  • b283da5 Merge pull request #643 from raymond-lam/issue617
  • 198a565 fix typo in parse-caching/Mustache.tags test
  • 2465398 Writer.prototype.parse to cache by tags in addition to template string

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 Aug 7, 2018

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