An in-range update of node-sass is breaking the build 🚨

[greenkeeper]

The devDependency node-sass was updated from 4.10.0 to 4.11.0.

🚨 View failing branch.

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

node-sass 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).

---

Release Notes for v4.11.0

LibSass 3.5.5

This released updates LibSass to 3.5.5. This update brings

• Stability fixes
• Removes noisey deprecation warning for @import'ing .css files
• Support hex colors with alpha channels

Features

• Update LibSass to 3.5.5 (@xzyfer, #2543)

Fixes

• Revert change that introduced a noisey deprecation warning (@xzyfer, #2362)

Supported Environments

OS	Architecture	Node
Windows	x86 & x64	0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11
OSX	x64	0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11
Linux*	x86 & x64	0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8**, 9**, 10**^, 11**
Alpine Linux	x64	4, 6, 7, 8, 9, 10, 11

*Linux support refers to Ubuntu, Debian, and CentOS 5+
** Not available on CentOS 5
^ Only available on x64

Commits

The new version differs by 9 commits.

• dfe1f05 Update changelog
• 8319be2 4.11.0
• 7929c32 Merge pull request #2543 from sass/libsass-subtreee
• ea9ffd6 Update sass-spec devDependency to use commit hash
• a6aab24 Remove call to removed sass_option_push_import_extension
• f06781d Merge commit '912301673420cdd8fbc1efcd09037206539915ee' as 'src/libsass'
• 9123016 Squashed 'src/libsass/' content from commit 39e30874
• 688d654 Remove committed src/libsass
• 9b7015c Update changelog

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]

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