Ruby Sass deprecated in March 2019

[DirtyF]

Current Sass post-install message warning:

Ruby Sass is deprecated and will be unmaintained as of 26 March 2019.

• If you use Sass as a command-line tool, we recommend using Dart Sass, the new
  primary implementation: https://sass-lang.com/install

• If you use Sass as a plug-in for a Ruby web framework, we recommend using the
  sassc gem: https://github.com/sass/sassc-ruby#readme

• For more details, please refer to the Sass blog:
  http://sass.logdown.com/posts/7081811

[pathawks]

The sassc-ruby Gem is the officially recommended alternative.

Hopefully somebody will step up and make sure everything works before March 🤷‍♂️

[Harald-LB]

There is already a pull request from csuhta to remove all dependencies on Ruby Sass in sassc-ruby.

[DirtyF]

sassc-ruby 2.0 has been released 🎉
https://github.com/sass/sassc-ruby/releases/tag/v2.0.0

[apjanke]

Will there be a new point release of jekyll-sass-converter to pick up this change some time soon? It looks like the most recent release, 1.5.2, is still using the sass gem, so I (and I assume other users) am still seeing this warning message when doing a bundle install/update for GitHub Pages sites.

[ashmaroli]

@apjanke There won't be a point release.
The version to support sassc over sass will be a 2.0.0. Jekyll 3.8 and older will not be making the switch.
Instead only Jekyll 4.0 and beyond will be able to use jekyll-sass-converter-2.0.0 out-of-the-box.
We're waiting for the libsass team to ship a new release that involves bug-fixes that allows for using sassc properly on Windows..

[apjanke]

Good to know. Thanks!

[RobertoMachorro]

@apjanke There won't be a point release.
The version to support sassc over sass will be a 2.0.0. Jekyll 3.8 and older will not be making the switch.
Instead only Jekyll 4.0 and beyond will be able to use jekyll-sass-converter-2.0.0 out-of-the-box.
We're waiting for the libsass team to ship a new release that involves bug-fixes that allows for using sassc properly on Windows..

For anyone that was as confused as I was to why this was closed, the explanation by @ashmaroli is the answer. We are stuck with it until Jekyll 4.0. Since we are stable with 3.8.6, we should be ok for now. Ignoring the deprecation message.