use YAML.unsafe_load to support Ruby 3.1/Psych 4 #2541
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since
YAML.load
has been changed to an alias ofPsych.safe_load
from Ruby 3.1/Psych 4.0, using Date, Time, etc. cause raise owing to prohibiting of class loading at frontmatter.ruby/psych#487
To avoid this problem, use
YAML.unsafe_load
if it is definded (YAML.load
is renamed toYAML.unsafe_load
).I think this is better implementation because
but you can choose passing
permitted_classes
option toYAML.load
to fix vulnerability.