build(deps): bump activestorage from 8.1.3 to 8.1.3.1

[dependabot]

Bumps activestorage from 8.1.3 to 8.1.3.1.

Release notes

Sourced from activestorage's releases.

8.1.3.1

Active Support

• No changes.

Active Model

• No changes.

Active Record

• No changes.

Action View

• No changes.

Action Pack

• No changes.

Active Job

• No changes.

Action Mailer

• No changes.

Action Cable

• No changes.

Active Storage

• Disable libvips's unfuzzed image loaders and savers.

  libvips flags some of its loaders and savers as "unfuzzed" or "untrusted", meaning they are only safe for trusted content. Active Storage will call Vips.block_untrusted(true) to disable them while booting. An application that needs a specific loader or saver may re-enable it in an initializer.

... (truncated)

Changelog

Sourced from activestorage's changelog.

Rails 8.1.3.1 (July 29, 2026)

• Disable libvips's unfuzzed image loaders and savers.

  libvips flags some of its loaders and savers as "unfuzzed" or "untrusted", meaning they are only safe for trusted content. Active Storage will call Vips.block_untrusted(true) to disable them while booting. An application that needs a specific loader or saver may re-enable it in an initializer.

  This is a breaking change for applications that process image types with an unfuzzed loader or saver. Variant transformation of BMP, ICO, and PSD attachments will raise Vips::Error, and analysis of these and other types such as SVG, JPEG XL, JPEG 2000, and Netpbm will no longer record width and height. Requesting an unfuzzed output format, typically FITS, JXL, or anything delegated to ImageMagick, will also raise Vips::Error. Attaching, storing, and downloading are unchanged.

  An application seeing Vips::Error raised during image transformation may wish to remove the affected content types from config.active_storage.variable_content_types in an initializer. Active Storage will then treat those attachments as not variable and will not generate variants for them. This most often matters to an application that transforms images during a request rather than in a background job, where the failure surfaces as an error response instead of a failed job.

  Rails.application.config.active_storage.variable_content_types -=
    %w[ image/bmp image/vnd.microsoft.icon image/vnd.adobe.photoshop ]

  Applications using the :mini_magick variant processor will see no change in how their attachments are processed, but the loaders and savers will be disabled process-wide whenever ruby-vips is installed, and the version requirements below will still apply. Such an application may remove ruby-vips from its Gemfile to avoid both.

  The minimum supported version of libvips is now 8.13, and the minimum supported version of ruby-vips is now 2.2.1. These are the earliest versions that are capable of disabling untrusted operations. When ruby-vips is installed and either minimum is not met, Active Storage will raise a RuntimeError while booting rather than run in an unsecurable environment.

  [GHSA-xr9x-r78c-5hrm] [CVE-2026-66066]

  Mike Dalessio

Commits

• 3989ebf Preparing for 8.1.3.1 release
• 349e7a5 Disable libvips's unfuzzed image loaders and savers
• See full diff 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 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)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity

Metric	Results
Complexity	0

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[codacy-production]

Pull Request Overview

While Codacy indicates the changes are up to standards, there is an implementation gap: the PR does not update config.active_storage.variable_content_types as recommended by the security advisory for CVE-2026-66066. This omission could lead to unhandled exceptions when the application processes untrusted image formats. Furthermore, ensure that all deployment environments have compatible system libraries, as the updated dependency will trigger a RuntimeError at boot if the underlying requirements are not met.

About this PR

• The security advisory recommends updating config.active_storage.variable_content_types to exclude blocked formats. This configuration change is missing from the current PR and should be added to ensure the application correctly handles the security restrictions.
• The application will now raise a RuntimeError at boot if the system libvips or ruby-vips dependencies do not meet the new minimum requirements. Ensure CI and production environments are verified for compatibility before merging.
• This update introduces a breaking change for applications processing specific image types such as BMP, ICO, PSD, SVG, and JPEG XL. These formats are now blocked by default, which may result in exceptions or missing metadata during processing.

Test suggestions

• Verify application boots successfully with the new Active Storage initialization logic.
• Verify standard image variants (PNG, JPEG) still generate correctly.
• Verify behavior for 'untrusted' formats like BMP, PSD, or ICO (expecting Vips::Error or missing metadata).

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. Verify application boots successfully with the new Active Storage initialization logic.
2. Verify standard image variants (PNG, JPEG) still generate correctly.
3. Verify behavior for 'untrusted' formats like BMP, PSD, or ICO (expecting Vips::Error or missing metadata).

_{TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback}