From 70694af18cf904285783ad3978d087e8db78248f Mon Sep 17 00:00:00 2001 From: Joe Rafaniello Date: Wed, 20 Nov 2024 17:01:12 -0500 Subject: [PATCH] Upgrade to latest 5.x version for rails 7.1 compatibility I noticed deep_merge was behaving differently in tests and failing on 7.1. Digging in, rails 7.0 was using the gem, 7.1 was using the activesupport module: rails 7.1: ``` (byebug) {}.method(:deep_merge) # ``` rails 7.0: ``` (byebug) {}.method(:deep_merge) # ``` Rails 7.1 changed the way their deep_merge is defined via a refactored module: https://www.github.com/rails/rails/commit/43b980368a7628fac95cc4f673e0dfbcee77c10b This was raised in: https://www.github.com/rails/rails/issues/49457 Config gem fixed this in 5.0 and subsequently fixed another compatibility issue in 5.1 https://www.github.com/rubyconfig/config/commit/759c0fe271b4b90d534217a5b6e0653d0c94ee85 --- Gemfile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Gemfile b/Gemfile index 6e26c4bc037..d82b69247bc 100644 --- a/Gemfile +++ b/Gemfile @@ -31,7 +31,7 @@ gem "bootsnap", ">= 1.8.1", :require => false # gem "bundler", "~> 2.2", ">= 2.2.15", *("!= 2.5.0".."!= 2.5.9"), "!= 2.5.19", :require => false gem "byebug", :require => false gem "color", "~>1.8" -gem "config", "~>2.2", ">=2.2.3", :require => false +gem "config", "~>5.1", :require => false gem "connection_pool", :require => false # For Dalli gem "dalli", "~>3.2.3", :require => false gem "default_value_for", "~>4.0"