-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
An in-range update of node-sass is breaking the build 🚨 #287
Comments
After pinning to 4.7.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Version 4.8.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 4.8.3 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv4.8.3FeaturesFixes
Supported Environments
*Linux support refers to Ubuntu, Debian, and CentOS 5+ CommitsThe new version differs by 9 commits.
See the full diff |
Version 4.9.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv4.9.0Deprecations
This behaviour violates the Sass language specification. Additionally it makes it impossible to output to the input directory via the CLI or watcher. Community
Features
Fixes
Misc
Supported Environments
*Linux support refers to Ubuntu, Debian, and CentOS 5+ CommitsThe new version differs by 13 commits.
See the full diff |
Version 4.9.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv4.9.1Community
FixesSupported Environments
*Linux support refers to Ubuntu, Debian, and CentOS 5+ CommitsThe new version differs by 21 commits.
There are 21 commits in total. See the full diff |
Version 4.9.2 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv4.9.2Community
Supported Environments
*Linux support refers to Ubuntu, Debian, and CentOS 5+ |
Version 4.9.3 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv4.9.3CommunityFixes |
☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.
Version 4.8.0 of node-sass was just published.
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
Release Notes
v4.8.0Features
Note: Node 10 is not officially supported until it's stable.
Fixes
.editorconfig
(@iamandrewluca, #2214)--quite
not quieting all informational output (@xzyfer)Misc
Supported Environments
*Linux support refers to Ubuntu, Debian, and CentOS 5+
Commits
The new version differs by 18 commits.
0b6baf3
4.8.0
7355176
Update CHANGELOG
3898350
Install script should not write partially downloaded binaries
3331891
Add SASS_BINARY_DIR to Readme
1ed5ce9
Allow setting of SASS_BINARY_DIR without setting explicit binary name
b926705
Use watcher removed function on deleted
a2d2a63
Pre-empt support for Node 10
863f29f
Bump minimum nan@2.9.2
0626988
docs: updated @10xLaCroixDrinker's username
fe572eb
Bump LibSass to 3.5.0
639173e
Bump sass-spec@3.5.0
78a74e9
Don't emit info output in quiet mode
dd805fc
Emit normal output as info not warn
abbc657
Use HTML comments to show a reduced Markdown
e797a34
build: Add back Appveyor 0.12-3 (#2255)
There are 18 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 🌴
The text was updated successfully, but these errors were encountered: