Rails adds a Hotwire guide and stops truncating 19-digit integers to 16 digits
The Rails core team has added an official guide on using Hotwire with Rails, readable now in the Edge Guides. It leads the 13 November edition of This Week in Rails, written by Wojtek, which otherwise lists a long round of fixes from 41 contributors.
The most consequential fix concerns integers. Strings cast by ActiveModel::Type::Integer are cut to limit * 4 bytes, and types without a limit, such as plain Active Model attributes, used a default limit of 4. A 19-digit value like "9223372036854775807" was therefore silently truncated to 16 digits. Types without a limit now use a 32-byte window, enough for any 64-bit value; types with an explicit limit keep their behaviour.
A query change comes with a deprecation. Passing an unqualified column to unscope(where: ...) currently removes conditions on every table that has a column of that name, including joined and eager-loaded tables. In Rails 9.0 it will only remove conditions on the relation's own table. A related fix qualifies unscope values with the table name when relations are merged.
Two fixes close leaks. ActiveSupport::EncryptedFile#inspect no longer prints the encryption key read from the key file or environment variable, which could previously end up in logs or error pages. And when an Action Cable channel action raised, the error log included the raw WebSocket message, writing in clear the values that filter_parameters hides in the debug log.
Time handling gets a correction as well. TimeZone#local, TimeZone#parse and TimeWithZone#change assumed every daylight-saving gap was one hour long, which overshot in zones with a shorter gap and mapped distinct local times onto the same instant in zones with a longer one. Local times in a gap are now shifted forward by the gap's actual length.
Smaller items include casting numeric values to the scale of the PostgreSQL money type, several preload fixes for has_many :through associations, and button_to now built on form_tag.

Why it matters
The integer and money fixes share a pattern: a value was stored or held in a form different from the one later read back, and nothing raised. Applications that keep 64-bit identifiers in Active Model attributes, outside the database schema, are the ones to check after upgrading.