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.
Hello lovely humans,
node-sass just published its new version 3.9.2.
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
JVM issues
In v3.9.0 we started publishing our full test suite to be compatible
with nodejs/citgm#165.
Turns out old Java API struggles with certain UTF-8 characters.
dlmanning/gulp-sass#529
#1699
This is affecting JVM based build systems like Jenkins
https://issues.jenkins-ci.org/browse/JENKINS-12610
https://issues.jenkins-ci.org/browse/JENKINS-33478
In this patch exclude an especially troublesome test file.
The new version differs by 44 commits .
2c2f6a2
3.9.2
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
There are 44 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade