Backporting Ruby 3.2 support to 4.x series

[janko]

It seems that Jekyll still has Liquid locked to versions 4.x, and it doesn't seem like this will change soon. It would be great if Ruby 3.2 support was backported to Liquid 4.x, as that should hopefully allow current Jekyll to run on Ruby 3.2 🙏🏻

[parkr]

This would be a fix for the largest number of people I think, since anything we do with Jekyll would require users to upgrade existing installations. An easier sell to GitHub Pages, too, I bet.

[parkr]

Cc github/pages-gem#859

[parkr]

@dylanahsmith Hey! I was looking at the Liquid 4.0.3 code and noticed that there's a taint_mode. Would you be interested in adding a quick patch for Liquid 4 which offers taint_mode = :off? or taint_mode = :disabled? This would disable all calls to tained? and untaint.

[markets]

That would be amazing! I'm also having problems running Jekyll (v3 and v4) with Ruby 3.2 (it goes fine with Ruby 3.3.0-dev btw). You can see the whole matrix here: markets/jekyll-timeago#36.

[dylanahsmith]

I've opened #1668 to backport ruby 3.2 support. However, we should really implement #1566 to get jekyll on liquid v5.

[dylanahsmith]

Fixed by #1668, and I've released liquid version 4.0.4 and liquid-c version 4.0.1

[janko]

Thank you for the fix, I really appreciate it! ❤️

[parkr]

Hugely appreciated, Dylan!