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 :muscle:
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 :sparkles:
You rock!
:palm_tree:
The new version differs by 55 commits (ahead by 55, behind by 1).
Coverage remained the same at 94.828% when pulling 4c6edf6703fab0223d3d55589b80e9326c31425d on greenkeeper-node-sass-3.9.1 into 5165805610a4ff418f50c2e8a016de2f0a5de592 on master.
Coverage remained the same at 94.828% when pulling 4c6edf6703fab0223d3d55589b80e9326c31425d on greenkeeper-node-sass-3.9.1 into 5165805610a4ff418f50c2e8a016de2f0a5de592 on master.
Coverage remained the same at 94.828% when pulling 4c6edf6703fab0223d3d55589b80e9326c31425d on greenkeeper-node-sass-3.9.1 into 5165805610a4ff418f50c2e8a016de2f0a5de592 on master.
Coverage remained the same at 94.828% when pulling 4c6edf6703fab0223d3d55589b80e9326c31425d on greenkeeper-node-sass-3.9.1 into 5165805610a4ff418f50c2e8a016de2f0a5de592 on master.
Hello lovely humans,
node-sass just published its new version 3.9.1.
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 :muscle:
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 :sparkles:
You rock!
:palm_tree:
The new version differs by 55 commits (ahead by 55, behind by 1).
3bc6165
3.9.1
23f3db3
Update changelog
4dcf37b
Exclude trouble utf-8 spec file name from npm
7f1332b
Update changelog
ac245a3
3.9.0
09204dd
Merge pull request #1697 from xzyfer/remove/cli-before
36cc5a0
Remove the cli before test
7c6ee13
Merge pull request #1520 from xzyfer/feat/appveyor-release-test
71d5d31
Merge pull request #1696 from xzyfer/feat/troubleshooting-docs
ff2b33f
Update some links and add example output to troubleshooting doc
4a0fcc2
update setup steps to comply with instructions
94471ab
Merge pull request #1593 from howlowck/patch-1
44f6edd
Merge pull request #1688 from xzyfer/feat/publish-tests
ba3a2e0
Merge pull request #1694 from xzyfer/feat/progress-bar
7bf34be
Merge pull request #1695 from xzyfer/feat/increase-timeout
There are 55 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade