Ruby on Rails v8.1.1 and v8.0.4 released!

[NewsBot]

Ruby on Rails v8.1.1 and v8.0.4 has been released.

Active Support

• No changes.

Active Model

• No changes.

Active Record

• No changes.

Action View

• Respect remove_hidden_field_autocomplete config in form builder hidden_field.

  Rafael Mendonça França

Action Pack

• Allow methods starting with underscore to be action methods.

  Disallowing methods starting with an underscore from being action methods
  was an unintended side effect of the performance optimization in
  207a254.

  Fixes #55985.

  Rafael Mendonça França

Active Job

• Only index new serializers.

  Jesse Sharps

Action Mailer

• No changes.

Action Cable

• No changes.

Active Storage

• No changes.

Action Mailbox

• No changes.

Action Text

• No changes.

Railties

• Do not assume and force SSL in production by default when using Kamal, to allow for out of the box Kamal deployments.

  It is still recommended to assume and force SSL in production as soon as you can.

  Jerome Dalbert

Guides

• No changes.

Link: Release 8.1.1 · rails/rails · GitHub

Active Support

• Fix Enumerable#sole to return the full tuple instead of just the first element of the tuple.

  Olivier Bellone

• Fix parallel tests hanging when worker processes die abruptly.

  Previously, if a worker process was killed (e.g., OOM killed, kill -9) during parallel
  test execution, the test suite would hang forever waiting for the dead worker.

  Joshua Young

• Fix NameError when class_attribute is defined on instance singleton classes.

  Previously, calling class_attribute on an instance’s singleton class would raise
  a NameError when accessing the attribute through the instance.

  object = MyClass.new object.singleton_class.class_attribute :foo, default: "bar" object.foo # previously raised NameError, now returns "bar" 

  Joshua Young

Active Model

• No changes.

Active Record

• Fix SQLite3 data loss during table alterations with CASCADE foreign keys.

  When altering a table in SQLite3 that is referenced by child tables with
  ON DELETE CASCADE foreign keys, ActiveRecord would silently delete all
  data from the child tables. This occurred because SQLite requires table
  recreation for schema changes, and during this process the original table
  is temporarily dropped, triggering CASCADE deletes on child tables.

  The root cause was incorrect ordering of operations. The original code
  wrapped disable_referential_integrity inside a transaction, but
  PRAGMA foreign_keys cannot be modified inside a transaction in SQLite -
  attempting to do so simply has no effect. This meant foreign keys remained
  enabled during table recreation, causing CASCADE deletes to fire.

  The fix reverses the order to follow the official SQLite 12-step ALTER TABLE
  procedure: disable_referential_integrity now wraps the transaction instead
  of being wrapped by it. This ensures foreign keys …

Link: Release 8.0.4 · rails/rails · GitHub