Drop explicit psych dependency - #17
Merged
Merged
Conversation
Psych ships as a default gem on Ruby >= 3.3, which this gemspec already requires, so pinning it as a runtime dependency is redundant. Mirrors ruby/rdoc#1725.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
spec.add_dependency "psych", ">= 4.0.0"line fromcode_manifest.gemspec.Gemfile.lockaccordingly.Psych ships as a default gem starting with Ruby 3.2, and this gemspec already requires Ruby >= 3.3, so declaring it as an explicit runtime dependency is unnecessary.
lib/code_manifest.rbstill doesrequire 'yaml', which continues to work as-is sinceyamlis itself a bundled default library that loads Psych internally. See ruby/rdoc#1725 for the same change made upstream in rdoc.Test plan
bundle exec rspecpasses (19 examples, 0 failures)bundle checkconfirms dependencies are satisfied