This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of node-sass.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
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.
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 expect this minor change to 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 was small, the failure was at times catastrophic.
Having this feature is important to us, but not breaking your build, and workflows is critical.
Hello lovely humans,
node-sass just published its new version 3.9.3.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of node-sass. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
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:
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 expect this minor change to 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 was small, the failure was at times catastrophic.
Having this feature is important to us, but not breaking your build, and workflows is critical.
The new version differs by 46 commits .
72af63e3.9.34cc86f7Revert to v3.9.02c2f6a23.9.23bc61653.9.123f3db3Update changelog4dcf37bExclude trouble utf-8 spec file name from npm7f1332bUpdate changelogac245a33.9.009204ddMerge pull request #1697 from xzyfer/remove/cli-before36cc5a0Remove the cli before test7c6ee13Merge pull request #1520 from xzyfer/feat/appveyor-release-test71d5d31Merge pull request #1696 from xzyfer/feat/troubleshooting-docsff2b33fUpdate some links and add example output to troubleshooting doc4a0fcc2update setup steps to comply with instructions94471abMerge pull request #1593 from howlowck/patch-1There are 46 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade