node-sass@4.2.0 passes

[greenkeeperio-bot]

Hello lovely humans,

node-sass just published its new version 4.2.0.

State	Failing tests 🚨
Dependency	node-sass
New version	4.2.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build went from success to failure.

As node-sass is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project ✨

You rock!

🌴

---

GitHub Release

LibSass to 3.4.3

LibSass has been bumped from 3.4.0 to 3.4.3. This update brings significant memory usage improvements. Check the LibSass changelogs for more information.

• 3.4.1
• 3.4.2
• 3.4.3

Fixes

• Increasing compile times in watcher (#1669)
• Stack depth counter leaking between processes (#1669)

---

The new version differs by 2 commits .

• 1e76d99 4.2.0
• 46266f1 LibSass 3.4.3 (#1848)

See the full diff.

---

This pull request was created by greenkeeper.io.

_{Tired of seeing this sponsor message? ⚡ greenkeeper upgrade}

[colinskow]

Restarted the failing job and it works. Travis just isn't very reliable for parallel tests.