Add constraint to ActiveSupport gem to use version lower than 7.1 #169
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.
Description
The latest version of
ActiveSupport
i.e.[7.1.0](https://rubygems.org/gems/activesupport/versions/7.1.0) - October 05, 2023 (250 KB)
has some issue with setting the default config to use its cache_format_version as 7.1.0 and picks 6.1 instead by default.This leads to a deprecation warning when using ActiveSupport Cache in our Faraday connection. Hence, until the ActiveSupport gem has a stable release and the issue is fixed, we continue to use the 7.0.x versions of ActiveSupport in our library.
Similar issue existed with 7.0.x - rails/rails#45293 which has been fixed.
Related Issue
Types of changes
Checklist:
Gemfile.lock
has changed, I have used--conservative
to do it and included the full output in the Description above.