3.1.4 can be a breaking change on projects without image_processing in their Gemfile

Hello

I have a Rails 8 project that doesn't have/use image_processing gem as a direct dependency, however it is included via carrierwave gem (not sure when this happened).

Since updating to 3.1.4 (from 3.1.3) that indirect dependency on image_processing is relaxed to allow 2.0+ (previously ~> 1.1), which brings in their breaking change for ruby-vips to now be a soft-dependency (ie. it must be added to the upstream Gemfile).

My project did not have image_processing directly so it also did not have ruby-vips, nor did my Docker image have the libvips package installed. This caused the app to fail to boot.

I'm not sure this is something that needs to be fixed in carrierwave (I caught the major version change when reviewing gem updates), I just wanted to document this use-case and the unexpected impact of updating a patch release of this gem. Perhaps it should have been kept back for the 4.0 release?

Kind regards