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.
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Hello lovely humans,
node-sass just published its new version 4.5.1.
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
Fixes
Supported Environments
*Linux support refers to Ubuntu, Debian, and CentOS 5
The new version differs by 305 commits .
f2b410b
Update changelog
86c600a
4.5.1
b0147a8
Merge pull request #1929 from xzyfer/support-node-8
7488f55
Make binding tests less fragile
10f9a58
Add Node 8 to the support versions lists
f2f4b96
Update link for VS 2013 download
7201e98
Update request version to avoid npm warn (#1915)
9905a59
Merge pull request #1885 from xzyfer/fix-rebuild
eb7f013
Add binding.js to Coveralls coverage (#1902)
f0419a7
Fix npm rebuild
cc7c3b3
4.5.0
c048687
Merge pull request #1877 from xzyfer/preserve-cwd-include-path
203f8d6
Mirror render and renderSync tests
4310623
Restore behaviour of cwd in include path
4271c70
Merge pull request #1874 from xzyfer/appveyor-release
There are 250 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.