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

Fix 6.1 compatability with ruby 2.5 #45593

Merged
merged 2 commits into from Jul 15, 2022

Conversation

skipkayhil
Copy link
Member

@skipkayhil skipkayhil commented Jul 13, 2022

Summary

Ruby 2.5 ships with Psych 3.0.x, which doesn't include keyword params
for permitted_classes.

Other Information

  • We could maybe make this metaprogramming like the respond_to? check, but the code complexity will really start to balloon
  • This probably won't apply cleanly to 6-0-stable or 5-2-stable unless Improve performance by removing respond_to? from runtime code #45578 is backported to those as well. I can make a new PR for the older branches if desired

Fixes #45590

Ruby 2.5 ships with Psych 3.0.x, which doesn't include keyword params
for permitted_classes.
@skipkayhil skipkayhil changed the title Fix compatability with ruby 2.5 Fix 6.1 compatability with ruby 2.5 Jul 13, 2022
@eileencodes eileencodes merged commit 571b4d5 into rails:6-1-stable Jul 15, 2022
eileencodes added a commit that referenced this pull request Jul 15, 2022
Fix 6.1 compatability with ruby 2.5
eileencodes added a commit that referenced this pull request Jul 15, 2022
Fix 6.1 compatability with ruby 2.5
@eileencodes
Copy link
Member

I backported this to 6-0-stable and 5-2-stable. Both required backports of other changes.

For anyone who ends up here, I'm not sure when we're going to do bugfix releases but it's highly unlikely 5-2-stable will get one. It's been EOL since June, this was the last security release of 5.2. If you need these changes, please point your gemfile at the 5-2-stable branch.

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

Successfully merging this pull request may close these issues.

None yet

2 participants