An in-range update of js-yaml is breaking the build 🚨

[greenkeeper[bot]]

The devDependency js-yaml was updated from 3.12.1 to 3.12.2.

🚨 View failing branch.

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

js-yaml is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

- ❌ **continuous-integration/travis-ci/push:** The Travis CI build could not complete due to an error ([Details](https://travis-ci.org/TailorDev/galaxy-tourbuilder/builds/498789187?utm_source=github_status&utm_medium=notification)).

---

Commits

The new version differs by 3 commits.

• e4267fc 3.12.2 released
• 7231a49 Browser files rebuild
• 99c0bf9 Fix for issue #468 includes passing test (#469)

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]]

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

[greenkeeper[bot]]

• The devDependency js-yaml was updated from 3.12.2 to 3.13.0.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 4 commits.

• 9d4ce5e 3.13.0 released
• f64c673 Browser files rebuild
• a567ef3 Restrict data types for object keys
• 59b6e76 Fix test name

See the full diff

[greenkeeper[bot]]

• The devDependency js-yaml was updated from 3.13.0 to 3.13.1.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 4 commits.

• 665aadd 3.13.1 released
• da8ecf2 Browser files rebuild
• b2f9e88 Merge pull request #480 from nodeca/toString
• e18afbf Fix possible code execution in (already unsafe) load()

See the full diff