Bump mini_magick from 4.13.2 to 5.1.2

[dependabot]

Bumps mini_magick from 4.13.2 to 5.1.2.

Release notes

Sourced from mini_magick's releases.

v5.1.1

• Add logger gem to dependencies for Ruby 3.4+.

v5.1.0

• New cli_env configuration was added for setting extra environment variables for every CLI command:

  MiniMagick.configure do |config|
    config.cli_env = { "MAGICK_MEMORY_LIMIT" => "128MiB" }
  end

• New graphicsmagick configuration was added for telling MiniMagick to use GraphicsMagick instead of MiniMagick:

  MiniMagick.configure do |config|
    config.graphicsmagick = true # prepend all commands with "gm"
  end

  Previously, the recommended approach was setting MiniMagick.cli_prefix = "gm", but that doesn't work when ImageMagick 7 is installed, as in that case MiniMagick will try to prepend magick on top of gm.

v5.0.1

• MiniMagick::Image#write doesn't delete the internal tempfile anymore, which restores use cases like:

  image = MiniMagick::Image.open("...")
  image.resize("500x500")
  image.write("foo.jpg")
  image.blur
  image.write("bar.png")

• Prevented MiniMagick::Image#to_ary being called by ruby in certain cases, such as [image].flatten(1).

v5.0.0

Improvements

• New class method shorthands were added for the tool API:

  # BEFORE
  MiniMagick::Tool::Convert.new { |convert| ... }
  MiniMagick::Tool::Identify.new { |convert| ... }
  # ...
  AFTER
  MiniMagick.convert { |convert| ... }
  MiniMagick.identify { |identify| ... }
  ...

... (truncated)

Commits

• 21b48d9 Bump to 5.1.2
• 53ea605 Add benchmark gem to dependencies
• 7c17853 Bump to 5.1.1
• 7c52f4b Test on Rubt 3.4
• a182d60 Add logger gem to dependencies
• 6737877 Bump to 5.1.0
• a3473ee Execute a spec only on Ruby 2.7+
• 8a7e56c Add MiniMagick.graphicsmagick for enabling GraphicsMagick
• 9c25a71 Remove WebMock depedency
• b9ab172 Allow setting time limit via MiniMagick.cli_env
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[sensei100]

Since this is a major version upgrade, we need to do some investigation to ensure that there are no breaking changes.

[nomadicoder]

@sensei100: I've checked this in a local development environment. All images that I am able to display locally look good, however there are images I am unable to display from S3. Will have to merge and deploy this change to QA in order to see how those images render.