Because Active Storage gem does not specify AWS SDK as its dependency, it’s quite possible you updated Active Storage while leaving AWS SDK behind (happened to me).

I make a file named: app/models/active_storage/attachment.rb. Because it's in your project it takes loading precedence over the Gem version. Then inside we load the Gem version, and then monkeypatch it using class_eval: active_storage_gem_path = Gem::Specification.find_by_name('activestorage').gem_dir require "#{active_storage_gem_path}/app/models/active_storage/attachment" ActiveStorage::Attachment.class_eval do acts_as_taggable on: :tags end The slightly nasty part is locating the original file, since we can't find it normally because our new file takes precedence. This is not necessary in production, so you could put a if Rails.env.production? around it if you like I think.

largest star sapphire

exe is the new bin

BTW, now bigdecimal is a default gem, so the version of bigdecimal is maintained independently. You can update default gems independently of Ruby version.

Mobility is cryptographically signed. To be sure the gem you install hasn't been tampered with, add my public key as a trusted certificate and install: gem cert --add <(curl -Ls https://raw.github.com/shioyama/mobility/master/certs/shioyama.pem) gem install mobility -P MediumSecurity The MediumSecurity trust profile will verify signed gems, but allow the installation of unsigned dependencies.

GitHub Packages uses the native package tooling commands you're already familiar with to publish and install package versions.