RepoJournal
Rails @rails
127 wires and counting

$ follow Rails

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

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-08-02
stories 29
GitHub RSS Archive Reviews Topics

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

RAILS DEPRECATES BINDS PARAMETER, UNIFIES REMOVAL TARGET TO 9.0

By RepoJournal · Filed · About Rails · Composed from the cited sources · methodology

kamipo Vipul A M
2 people shipped this
kamipo @kamipo 3 cited Vipul A M @vipulnsward 1 cited

Rails is killing the `binds` positional argument across `insert`, `update`, and `delete` after moving bind parameters into the Arel AST, forcing a migration to a cleaner API before Rails 9.0.

Kamipo merged the deprecation [1] that standardizes how raw SQL and bind parameters flow through write operations. The change follows a recent restoration [1] that kept legacy callers working while the codebase moved toward `Arel.sql("... ?", value)` syntax, which wraps SQL and binds together as a single `Arel::Nodes::BoundSqlLiteral` node. This aligns with how `Model.where("... = ?", value)` already works, eliminating the split between SQL and binds at the connection level. Alongside the deprecation, Rails unified the removal target across existing deprecations to Rails 9.0 [2], replacing the split between 8.3 and 9.0 removals so runtime messages and CHANGELOG entries point at the same horizon [2]. A follow-up aligned the default `deprecation_horizon` constant to match [3]. The Rails website published the July 31 newsletter [4] covering the week's PRs and foundation news across 15 merged changes and 25 contributors.

$ ls rails/reviews/ # the step-back reads

the week in review Active Storage gets a direct-upload kill switch the month in review Rails deepens Ractor safety, ships Marcel 2.0, and retires decade-old APIs
Topics: Ruby Full archive → Weekly reviews →

Quick answers

What shipped in Rails on August 2, 2026?
Rails is killing the `binds` positional argument across `insert`, `update`, and `delete` after moving bind parameters into the Arel AST, forcing a migration to a cleaner API before Rails 9.0. In total, 19 commits and 10 pull requests landed.
Who contributed to Rails on August 2, 2026?
2 developers shipped this update, including kamipo and Vipul A M.
What were the notable Rails updates?
Deprecate passing `binds` to `insert`, `update`, and `delete`, Unify deprecation removal target to Rails 9.0, and Align default `deprecation_horizon` with the rest of the codebase.
♥

$ log @rails --recent

Bootsnap guards d_type for Illumos, Rails trims Ractor test skips 17 shipped MySQL deadlock fix for find_or_create_by, Asset Pipeline guide rewrite 19 shipped kamipo retires three legacy Active Record holdovers 16 shipped Postgres index lookups scoped to the resolved table, mariadb replaces mysql5 in dbconsole 28 shipped

$ log --all # elsewhere on the wire

@openclaw Cold-start Gateway diagnostics stop crying wolf, doctor repairs plugin drift Agentic Coding Cline desktop bundles shrink, goose unblocks its own clicks

$ ls showcases/

Django Laravel Node.js Go Vercel Vue.js Kubernetes HashiCorp Arch Linux Linux Anthropic OpenAI

$ init your-desk

RepoJournal can write one of these for any repo you care about. Sign in with GitHub, pick your repos and sources, and your desk gets a wire like this one every morning.