Ruby on Rails v8.1.3.1, v8.0.5.1 and v7.2.3.2 released!

[NewsBot]

Ruby on Rails v8.1.3.1, v8.0.5.1 and v7.2.3.2 has been released.

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.

  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 c…

Link: Release 8.1.3.1 · rails/rails · GitHub

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.

  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 c…

Link: Release 8.0.5.1 · rails/rails · GitHub

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.

  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 c…

Link: Release 7.2.3.2 · rails/rails · GitHub