chore: relax faraday middleware version constraints #166
Conversation
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
Allow any 0.x version >= 0.3.0 instead of only 0.3.x to provide more flexibility for dependency resolution while still excluding potential breaking changes in 1.0.
Allow any 1.x version >= 1.0.4 instead of only 1.0.x to provide more flexibility for dependency resolution while still excluding potential breaking changes in 2.0.
|
Author
|
👋🏼 @armando-rodriguez-cko, could you take a look at this? Do you need anything else I can help with to move this forward? |
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
Relaxes version constraints for Faraday middleware dependencies to allow more flexibility in dependency resolution while still respecting semantic versioning boundaries.
Changes
Motivation
The previous constraints were overly restrictive, only allowing patch-level updates. This blocks dependency upgrades required to support Ruby 4.0.0, as newer versions of these gems include necessary compatibility fixes.
The new constraints follow semantic versioning principles: