bangbang93/freyja

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

greenkeeper opened this issue Β· 1 comments

The dependency node-sass was updated from 4.11.0 to 4.12.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 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 could not complete due to an error (Details).

Release Notes for v4.12.0

Features

Community

Dependencies

Supported Environments

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

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

Commits

The new version differs by 19 commits.

  • 23c8659 4.12.0
  • bc78b22 Merge pull request #2633 from xzyfer/node-12
  • 12c0052 Workaround waiting for AppVeyor to add Node versions
  • 9e564a1 Use explicit Node version numbers in CI config
  • 5aae0d2 Use Visual Studio 2017 for Node >= 10
  • 480250c Use g++4.9 for all Node >= 10 in Travis CI
  • f4eebc8 Node 12 requires at least nan@2.13.2
  • 34f99a2 Fix OSX compilation for Mojavi
  • da10866 Add support for Node 12
  • 0f86a0a Update README.md (#2617)
  • 33a32c3 https-ify sass-lang.com urls (#2608)
  • a2ac801 removed outdated TOC entries
  • 44366b3 Update lodash and remove prototype vulnerabilities
  • 088b80b Remove @adamyeats from maintainers list
  • 7c1dd8e Merge pull request #2454 from nschonni/troubleshooting-edits

There are 19 commits in total.

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 🌴

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