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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For better dependency management and to prevent potential future breakages, it's recommended to use a pessimistic version constraint.
While
>= 1.0.4
correctly resolves the security vulnerability, it allows any future version of theuri
gem, including major versions with breaking changes (e.g.,2.0.0
).Using
~> 1.0.4
(which is equivalent to>= 1.0.4
and< 1.1.0
) will ensure you get security patches within the1.0.x
series while protecting against breaking changes in future minor or major releases. This is also consistent with other versioned dependencies in this file likeqiita_marker
androuge
.This approach enhances the stability for consumers of this gem.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since it's a library, I don't think there's a strong need to pessimistic version.