RepoJournal
Rails

@rails

Ruby on Rails - Shopify, Basecamp, GitHub all run on it

Keep up with Rails in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

One email a day. Unsubscribe in one click.

Pick a date

Topics: Ruby Full archive →

The Wire · Showcase

Rails Adds RETURNING Support, PostgreSQL Virtual Columns Auto-Reload

By RepoJournal · Filed · About Rails

Rails shipped support for SQL RETURNING clauses across INSERT/UPDATE/DELETE operations, eliminating extra database round trips and reducing developer friction around stale data.

The big one: Arel now supports RETURNING clauses [1], which means your UPDATE and DELETE queries can fetch modified data in a single round trip instead of requiring a separate SELECT. Active Record is already leveraging this for PostgreSQL virtual columns, which now reload automatically on update without an extra query [2]. This is the kind of boring infrastructure work that makes deploys faster and schemas cleaner.

Action Text got more precise with its Direct Upload events [3], now dispatching both `id` and `file` properties as documented, plus two previously missing events for better upload lifecycle hooks. On the build side, the devcontainer now supports Ruby 4.0.4 [6], though you probably aren't running that in production yet. Sprockets fixed a gnarly asset fingerprinting issue where GZip mtime headers weren't being set correctly across Ruby versions [5], ensuring your cache busting works as intended.

One quality-of-life win: Rails generators now clean up stale new_framework_defaults files when you update load_defaults [4], so your app:update runs don't leave behind noise anymore. All of this ships together into a release that's heavy on database ergonomics and light on breaking changes.

One email a day. Unsubscribe in one click.

Action items

References

  1. [1] Add support for `RETURNING` to `INSERT`/`UPDATE`/`DELETE` statements ↗ rails/rails
  2. [2] PostgreSQL reload virtual columns on update via RETURNING clause ↗ rails/rails
  3. [3] Action Text: Dispatch Active Storage events with `id` and `file` ↗ rails/rails
  4. [4] Remove framework_defaults if load_defaults matches rails/rails
  5. [5] Do not set variable GZip#mtime but do always set File#mtime ↗ rails/sprockets
  6. [6] Add Ruby version: 4.0.4 ↗ rails/devcontainer

Quick answers

What shipped in Rails on May 15, 2026?
Rails shipped support for SQL RETURNING clauses across INSERT/UPDATE/DELETE operations, eliminating extra database round trips and reducing developer friction around stale data. In total, 28 commits, 16 pull requests, and 2 releases landed.
Who contributed to Rails on May 15, 2026?
5 developers shipped this update, including benedikt, abaldwin88, seanpdoyle, bensheldon, and rails-bot.
What were the notable Rails updates?
Add support for `RETURNING` to `INSERT`/`UPDATE`/`DELETE` statements, PostgreSQL reload virtual columns on update via RETURNING clause, and Action Text: Dispatch Active Storage events with `id` and `file`.

More from @rails

Daily updates, in your inbox

Follow Rails

Keep up with Rails in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

One email a day. Unsubscribe in one click. Read a past issue →

Elsewhere on the wire

Want every project, not just this one?