fix: relax json_api_client pin to support Ruby 4.0#90
Merged
Conversation
The exact pin '1.23.0' transitively forced faraday-gzip < 3.0, whose required_ruby_version < 4 blocked installing the gem on Ruby 4.0. json_api_client 1.24.0 raised the cap to faraday-gzip < 4.0 (allowing 3.x, which supports Ruby 4), so '~> 1.23' resolves the conflict while keeping the existing floor. Also add Ruby 4.0 to the CI matrix so this regression stays covered — nothing tested Ruby 4 before, which is why the conflict went unnoticed. Verified locally on Ruby 3.3: bundle resolves json_api_client 1.24.0 + faraday-gzip 3.1.0; 532 examples 0 failures; rubocop clean.
|
Merged
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.
Fixes #89.