Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build: update liquid to 4.0.4 #860

Merged
merged 1 commit into from
Feb 1, 2023

Conversation

gradybarrett
Copy link

@gradybarrett gradybarrett commented Jan 12, 2023

Ruby 3.2 removed the "tainted" interface, which liquid <=4.0.3
still uses. Liquid 4.0.4 removes references to this interface so that
it works with Ruby 3.2.

Closes #859.

@gradybarrett gradybarrett force-pushed the gradybarrett/liquid-v4-0-4 branch 2 times, most recently from 1a17219 to 899840d Compare January 12, 2023 22:47
@gradybarrett
Copy link
Author

@parkr hopefully this PR wasn't presumptuous. 😄

@parkr
Copy link
Contributor

parkr commented Jan 13, 2023

Nope! I can't merge this though since I don't work at GitHub anymore. Perhaps @yoannchaudet can help! This patched version fixes compatibility with Ruby 3.2.

@adhibsyed
Copy link

Would be great to have this merged.

@keithrbennett
Copy link

This issue is blocking the use of Ruby 3.2 for Github Pages sites. Could someone with the authority to merge it please take a look at it? It's a simple one-line fix. I can corroborate that tests pass with this change.

mmguero added a commit to mmguero-dev/jekyll-serve that referenced this pull request Jan 24, 2023
Ruby 3.2 removed the "tainted" interface, which liquid
>=4.0.3 still uses. Liquid 4.0.4 removes references to this
interface that it works with Ruby 3.2.

Closes github#859.
@gradybarrett
Copy link
Author

Updated the branch and fixed my gpg config.

@vhxs
Copy link

vhxs commented Jan 25, 2023

+1 please merge this in, I've had to explicitly point my blog towards this forked repo

@JonathanCopeland
Copy link

Can confirm this is still a problem, I'm receiving:
Liquid Exception: undefined method `tainted?' for ...

Any ETA on when this will be merged?

@yoannchaudet
Copy link
Contributor

Surfacing that to the team, we will look at it shortly and make a round of update.

@parkr
Copy link
Contributor

parkr commented Jan 27, 2023

@yoannchaudet I'm making a bug patch release of Jekyll soon that allows y'all to also upgrade i18n and tzinfo, if you want to bundle this patch release into your round of updates: jekyll/jekyll#9282

@surelynottrue
Copy link

Is there any solution in place for this? This error is not allowing me to push any changes to my Jekyll website :)

@JonathanCopeland
Copy link

Same

@parkr
Copy link
Contributor

parkr commented Jan 31, 2023

Hopefully you upgrade the Ruby used by your Jekyll site independently from other apps you maintain! I personally always run CI with any ruby or gem updates before merging. Then I can still push updates to my site while I wait for the update to be compatible. I recommend rbenv for maintaining several different Ruby versions on the same system.

@tsusdere tsusdere merged commit b0f457c into github:master Feb 1, 2023
@gradybarrett gradybarrett deleted the gradybarrett/liquid-v4-0-4 branch February 2, 2023 00:56
@JonathanCopeland
Copy link

Hey everyone, I'm probably missing something, but after running bundle update github-pages I'm still getting the tainted error. Is there anything else that I need to do to serve my site locally?

@yoannchaudet
Copy link
Contributor

yoannchaudet commented Feb 2, 2023

The gem has not been fully propagated in the systems. It is being updated today. https://pages.github.com/versions/ will report it as soon as it's there.

@parkr parkr mentioned this pull request Feb 2, 2023
@yoannchaudet
Copy link
Contributor

We should be good now: https://pages.github.com/versions. Still updating our legacy build infra but build on Actions are already current.

@parkr
Copy link
Contributor

parkr commented Feb 3, 2023

Thank you so much, @yoannchaudet!

@JonathanCopeland
Copy link

Working 100%. Thank you very much @yoannchaudet

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Error: undefined method tainted? when using Ruby v3.2.0
10 participants