Who contributed to Rails on July 29, 2026?

7 developers shipped this update, including fatkodima, Kenta Ishizaki, chad-cole, Ryuta Kamizono, hmcguire-shopify, Hartley McGuire, and dependabot.

What were the notable Rails updates?

Merge pull request #58235 from 55728/remove-stale-requires, Remove unreachable single-version branch from `DefaultSchemaVersionsFormatter`, and Simplify `insert` callers to only pass what they need.

@rails

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

github ↗

Pick a date

Topics: Ruby Full archive →

The Wire · Showcase

RAILS CORE DUMPS LEGACY CODE, RAISES SQLITE FLOOR

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

7 people shipped this

dependabot @dependabot 3 cited

Ryuta Kamizono @kamipo 2 cited

fatkodima @fatkodima 1 cited

Kenta Ishizaki @55728 1 cited

chad-cole @chad-cole 1 cited

hmcguire-shopify @hmcguire-shopify 1 cited

Hartley McGuire @skipkayhil

Rails is ripping out stale compatibility layers while enforcing a modern SQLite baseline, signaling the framework is shedding technical debt faster than the ecosystem moves.

The main Rails repository just merged a series of pruning commits that remove unreachable code paths and drop unnecessary positional arguments from core insertion logic [1] [2] [3]. This isn't housekeeping for its own sake. It's a signal that Rails is aggressively simplifying the codebase by eliminating fallbacks nobody uses anymore. In parallel, the team bumped the minimum SQLite version to 3.35.0 [4], which means systems still running SQLite 3.23 through 3.34 are now officially unsupported and will see broken auto-generated primary keys. The RETURNING clause that Rails leaned on since 7.1 had no fallback, so this bump just makes that contract explicit. Token authentication in HTTP modules now passes scheme information to the authentication block [5], giving controllers finer control over how they validate incoming credentials. Over in the supporting ecosystem, Propshaft merged style enforcement tooling [6], and solid_cache picked up security patches for JSON buffer overflow, HTML sanitizer SVG handling, and Loofah numeric character reference parsing [7] [8] [9]. The pace of consolidation across these three repos—38 commits and 24 PRs in 24 hours—shows Rails isn't slowing down.

Action items

→ Verify your SQLite version is 3.35.0 or higher before next deploy rails/rails [plan]
→ Review HTTP token authentication callsites to use the new scheme parameter rails/rails [monitor]
→ Update solid_cache dependencies to pull in JSON and Loofah security patches rails/solid_cache [plan]

References

[1] Merge pull request #58235 from 55728/remove-stale-requires rails/rails
[2] Remove unreachable single-version branch from `DefaultSchemaVersionsFormatter` rails/rails
[3] Simplify `insert` callers to only pass what they need rails/rails
[4] Bump the minimum supported SQLite version to 3.35.0 rails/rails
[5] Pass scheme to token authentication block in http_atthentication ↗ rails/rails
[6] Add `rubocop-rails-omakase`, enable frozen string literals ↗ rails/propshaft
[7] Bump json from 2.19.2 to 2.19.9 ↗ rails/solid_cache
[8] Bump rails-html-sanitizer from 1.7.0 to 1.7.1 ↗ rails/solid_cache
[9] Bump loofah from 2.25.1 to 2.25.2 ↗ rails/solid_cache

Quick answers

What shipped in Rails on July 29, 2026?: Rails is ripping out stale compatibility layers while enforcing a modern SQLite baseline, signaling the framework is shedding technical debt faster than the ecosystem moves. In total, 38 commits and 24 pull requests landed.
Who contributed to Rails on July 29, 2026?: 7 developers shipped this update, including fatkodima, Kenta Ishizaki, chad-cole, Ryuta Kamizono, hmcguire-shopify, Hartley McGuire, and dependabot.
What were the notable Rails updates?: Merge pull request #58235 from 55728/remove-stale-requires, Remove unreachable single-version branch from `DefaultSchemaVersionsFormatter`, and Simplify `insert` callers to only pass what they need.

SOLID_QUEUE FIXES RAILS 8.1 CONNECTION CHECKOUT CLASH

Solid Queue patched a critical incompatibility with Rails 8.1's permanent connection checkout mode that breaks the new DistinctValues module.

ruby 8 shipped 1-min read

@rails 2 days ago

RAILS CLEANS UP DATABASE ADAPTER CRUFT, MARKS INSERT_RETURNING FOR REMOVAL

Rails is deprecating the `insert_returning` option after it became redundant across multiple insert paths, while extracting hidden parameters and removing dead code across the database layer.

ruby 24 shipped 1-min read

@rails 3 days ago

Rails drops Python 2 relics, tightens TimeZone validation

Rails is removing ruby2_keywords shims across the codebase now that Ruby 3.3.1 is the minimum, while TimeZone#parse gets stricter about invalid input.

ruby 22 shipped 1-min read

@rails 4 days ago

RAILS 8 LAZY ROUTES NOW THREAD-SAFE, SOLID QUEUE ADDS MIGRATION GENERATOR

A race condition in Rails 8's deferred route loading could serve 404s on valid routes under concurrent requests, and a fix landed overnight.

ruby 18 shipped 1-min read

Elsewhere on the wire

AI Agents about 4 hours ago

LANGCHAIN CORES SHIP, ANTHROPIC THINKING BLOCKS FIXED, OPENHANDS TIGHTENS WEBSOCKET AUTH

LangChain released two core packages with critical fixes for streaming stability and environment variable handling, while OpenHands closed a security gap that left WebSocket connections unprotected.

ai-agents 119 shipped 1-min read

Local LLMs about 4 hours ago

OLLAMA RIPS OUT IMAGE GENERATION, LLAMA.CPP SHIPS SPECULATIVE DECODING

Ollama removed its entire MLX image generation pipeline overnight, while llama.cpp landed DSpark speculative decoding and fixed a critical SYCL memory bug affecting Arc GPUs.

+11

llms 239 shipped 2-min read

@CachyOS about 4 hours ago

KERNEL SCHEDULER UPDATES ACROSS BORE AND SCX TOOLING

CachyOS shipped BORE 6.8.0 patches across two kernel series while upgrading its sched-ext ecosystem in parallel, signaling major tuning work ahead.

infra 83 shipped 1-min read

Elixir & Phoenix about 4 hours ago

ELIXIR TIGHTENS ERROR HANDLING ACROSS DATE, ECTO, AND IEXHELPERS

Date.range now surfaces ArgumentError instead of Protocol.UndefinedError when passed invalid step values, catching a class of bugs that silently fail in production code.