What shipped in Rails on July 13, 2026?

SQLite3 migrations just stopped silently destroying the wrong foreign keys. In total, 16 commits and 8 pull requests landed.

Who contributed to Rails on July 13, 2026?

4 developers shipped this update, including Xavier Noria, Kenta Ishizaki, fatkodima, and Diogo Vernier.

What were the notable Rails updates?

Read foreign key names from the schema on SQLite3, Honor if_not_exists in SQLite3 add_check_constraint and add_foreign_key, and Merge pull request #58091 from 55728/fix-sqlite3-add-check-constraint-if-not-exists.

@rails

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

github ↗

Pick a date

Topics: Ruby Full archive →

The Wire · Showcase

SQLITE3 FOREIGN KEYS GET THEIR NAMES BACK

By RepoJournal · Filed 06:55 UTC on July 13, 2026 · About Rails

4 people shipped this

Kenta Ishizaki @55728 2 cited

fatkodima @fatkodima 2 cited

Xavier Noria @fxn 1 cited

Diogo Vernier @diogovernier 1 cited

SQLite3 migrations just stopped silently destroying the wrong foreign keys.

Rails merged three critical fixes for SQLite3 schema introspection that were causing migrations to behave unpredictably [1]. The core issue: `foreign_keys` wasn't reading constraint names from the schema, so every `ForeignKeyDefinition` came back with `name == nil`. This meant `remove_foreign_key(table, name: "fk")` ignored your target constraint and deleted an arbitrary one instead [1]. The same blind spot broke `if_not_exists:` on both `add_check_constraint` and `add_foreign_key` [2], leaving SQLite3 users without options that MySQL and PostgreSQL had long since fixed. Two merges landed overnight: one restoring name reading from the schema [3], the other honoring the `if_not_exists:` flag in adds and removes [2]. Rails also landed a quality-of-life fix letting `relative_time_in_words` accept `Date` and numeric inputs directly [4], plus a cleanup removing unnecessary reverse calls [5]. Over in Solid Queue, the Puma plugin tests got smarter about port allocation, ditching hardcoded 9222 for dynamic assignment to stop EADDRINUSE cascade failures [6].

Action items

→ If you use SQLite3 and migrations that target foreign keys by name, pull the latest main before your next deploy rails/rails [immediate]
→ Review any SQLite3 migrations that rely on add_check_constraint or add_foreign_key with if_not_exists to confirm they work as intended rails/rails [plan]
→ Update Solid Queue if you run its test suite and see port binding flakes rails/solid_queue [monitor]

References

[1] Read foreign key names from the schema on SQLite3 rails/rails
[2] Honor if_not_exists in SQLite3 add_check_constraint and add_foreign_key rails/rails
[3] Merge pull request #58091 from 55728/fix-sqlite3-add-check-constraint-if-not-exists rails/rails
[4] Merge pull request #58092 from 55728/fix-relative-time-in-words-non-time-inputs rails/rails
[5] Remove unnecessary reverse call rails/rails
[6] Use dynamic port allocation in Puma plugin tests rails/solid_queue

Quick answers

What shipped in Rails on July 13, 2026?: SQLite3 migrations just stopped silently destroying the wrong foreign keys. In total, 16 commits and 8 pull requests landed.
Who contributed to Rails on July 13, 2026?: 4 developers shipped this update, including Xavier Noria, Kenta Ishizaki, fatkodima, and Diogo Vernier.
What were the notable Rails updates?: Read foreign key names from the schema on SQLite3, Honor if_not_exists in SQLite3 add_check_constraint and add_foreign_key, and Merge pull request #58091 from 55728/fix-sqlite3-add-check-constraint-if-not-exists.

RAILS TIGHTENS DESERIALIZATION ERROR HANDLING, PROPSHAFT EYES RUBY 4

Rails introduces a targeted deserialization error for orphaned job records, solving a production pain point at HEY while ActiveJob remains resilient.

ruby 12 shipped 1-min read

@rails 3 days ago

RAILS FIXES FROZEN CACHE BUGS IN RACTORIZED APPS, SOLID QUEUE CATCHES UP

Rails shipped fixes for FrozenErrors that break ractorized applications when caches freeze with the app, while Solid Queue patched a breaking change in ActiveJob's shutdown protocol.

ruby 11 shipped 1-min read

@rails 4 days ago

RAILS CLEANS UP FORM HELPERS WHILE RACTOR SUPPORT EXPANDS

Rails merged a refactor that eliminates duplication in ColorField rendering, while core work continues on Ractor integration for multi-threaded applications.

ruby 17 shipped 1-min read

@rails 5 days ago

RAILS FIXES STREAMING HANG ON CLIENT DISCONNECT, TACKLES FOREIGN KEY EDGE CASES

ActionController::Live streams were leaving reader threads blocked indefinitely when clients disconnected fast - Rails just fixed the race condition that's been haunting production deploys.

ruby 39 shipped 1-min read

— or follow the whole beat:

Elsewhere on the wire

Elixir & Phoenix about 6 hours ago

ELIXIR FIXES SPEC AND ARITY BUGS ACROSS CORE MODULES

Elixir core shipped three precision fixes overnight that tighten specs on IEx and EEx utilities, catching the kind of type mismatches that slip past dialyzer.

elixir 7 shipped 1-min read

Mobile platforms about 6 hours ago

FLUTTER CLEANS HOUSE ON ANALYSIS RULES WHILE SWIFT FIXES C-INTEROP CRASHES

Flutter is migrating away from deprecated strict analysis modes in favor of lint rules, while Swift patches critical crashes in bit-field accessors and C interoperability.

mobile 21 shipped 1-min read

@dotnet about 6 hours ago

ASPNETCORE VALIDATION GENERATOR FIXED, MSBUILD SYNCS ROSLYN AND NUGET

ASP.NET Core's validation source generator now correctly unwraps array types, closing a gap that could slip validation past your models.

dotnet 6 shipped 1-min read

@spring-projects about 6 hours ago

SPRING-AI FIXES CRITICAL TOOL CALLING BUG THAT BROKE OPENAI STRICT MODE

The `strict` parameter in OpenAI tool calling was silently failing across all Spring AI implementations because it was serialized in the wrong place in the payload.

java 8 shipped 1-min read