We are getting the following error in staging when faraday gem is updated from 2.7.10 -> 2.7.11 and newrelic 9.5.0 -> 9.6.0
You have already activated base64 0.1.0, but your Gemfile requires base64 0.1.1. Since base64 is a default gem, you can either remove your dependency on it or try updating to a newer version of bundler that supports base64 as a default gem. (Gem::LoadError)
this error pops in staging which runs apache/mod-passenger web sever and is not reproducable when running app with thin server or passenger stand-alone server.
Both faraday 2.7.11 and newrelic 9.6.0 gems add base64 gem dependency which triggers the install of 0.1.1+ base64 gem but passenger seem to pick up base64 library v0.1.0 which is bundled in with ruby 3.0.6.
the solution is to pin base64 to v0.1.0 in the Gemfile
We are getting the following error in staging when faraday gem is updated from 2.7.10 -> 2.7.11 and newrelic 9.5.0 -> 9.6.0
this error pops in staging which runs apache/mod-passenger web sever and is not reproducable when running app with thin server or passenger stand-alone server.
Both faraday 2.7.11 and newrelic 9.6.0 gems add base64 gem dependency which triggers the install of 0.1.1+ base64 gem but passenger seem to pick up base64 library v0.1.0 which is bundled in with ruby 3.0.6.
the solution is to pin base64 to v0.1.0 in the Gemfile