Relax highline dependency to allow versions 1.6.X #19
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.
Hey @ahoward 👋
In the process of upgrading a legacy code base to ruby 3.1 I noticed an issue with sekrets/openssl. The code base is running sekrets 1.13 and I noticed that sekrets 1.14 would fix the issue.
Unfortunately sekrets 1.14 also bumped the highline dependency from 1.6 to 1.7 and our code base has a hard dependency on highline 1.6, so we currently cannot use sekrets 1.14.
With this PR I propose to relax the highline dependency to allow for highline versions 1.6.X again. My reasons for doing so are (besides being more "inclusive" and allowing us to use 1.14 😉):
In general I think gems should be as loose as possible with dependencies on other gems.
Let me know if this makes sense to you!