Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello lovely humans,
node-sass just published its new version 3.9.3.
This version is covered by your current version range, but I could not detect automated tests for this project. Without a test suite I can not really tell whether your project still works.
I was looking at the latest commit of your default branch, but GitHub said there is no status attached to it.
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
Fix filename issues 🚑
In v3.9.0 we began publishing our test suite to npm as part of our release. We did this be compliant with the node-citgm project. Being the citgm would give us early warning of changes in Node that would break Node Sass for users. We'd hoped this would allows to address these issue early and avoid the dozens of bug reports we receive.
However some users have experience issues with some test filenames include unicode characters. Some npm@2 users have also experienced issues with our path names being too long.
As a result we're temporarily reverting the addition of our test suite until we have a solution for these issues.
We're sorry 💖
Noone ever wants to break someone's build. We had expected this minor change to be innocuous.
Unfortunately we had not accounted for the variety of operating environments our +2M monthly downloads would be running on. Although the number of affected users was small, the failure was at times catastrophic.
Having this feature is important to us, but not breaking your builds, and workflows is critical.
The new version differs by 2 commits .
72af63e
3.9.3
4cc86f7
Revert to v3.9.0
See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡
greenkeeper upgrade