An in-range update of js-yaml is breaking the build 🚨
- Dominant language
- JavaScript
- Stars
- 37
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
## Version **3.9.0** of [js-yaml](https://github.com/nodeca/js-yaml) just got published.
Branch
Build failing 🚨
Dependency
js-yaml
Current Version
3.8.4
Type
dependency
This version is **covered** by your **current version range** and after updating it in your project **the build failed**.
js-yaml is a direct dependency of this project **this is very likely breaking your project right now**. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this :muscle:
Status Details
- ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/hax/babel-features/builds/251429212?utm_source=github_status&utm_medium=notification)
---
Commits
The new version differs by 9 commits.
d411edd3.9.0 released1b45eccBrowser files rebuild561891ceslint & CS updated87c338Deps bump8249deaUpdate changelog2cd3b01add missed test filesb76645eTravis: add node.js v83c148e2Support loadAll/safeLoadAdd without iterator (return array), #350bd32506AddcondenseFlowoption, close #346
See the full diff
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).
---
Your [Greenkeeper](https://greenkeeper.io) Bot :palm_tree:
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.