Who contributed to Rails on June 18, 2026?

4 developers shipped this update, including viralpraxis, andrewn617, skipkayhil, and jordan-brough.

What were the notable Rails updates?

Merge pull request #57758 from viralpraxis/fix-in-order-of-raising-on-cte, Fix `in_order_of` raising on CTEs, and Make AbstractController::Helper.helper_method ractor safe.

@rails

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

github ↗

Pick a date

Topics: Ruby Full archive →

The Wire · Showcase

RAILS FIXES CTE ORDERING BUG, TAILWIND TAMES ORPHANED PROCESSES

By RepoJournal · Filed 06:00 UTC on June 18, 2026 · About Rails

4 people shipped this

viralpraxis @viralpraxis 1 cited

andrewn617 @andrewn617 1 cited

skipkayhil @skipkayhil 1 cited

jordan-brough @jordan-brough 1 cited

Rails patched a `in_order_of` crash when querying Common Table Expressions, while tailwindcss-rails 4.6.0 finally kills zombie watchers that plague foreman-based development.

The Rails team merged a fix [1] for `in_order_of` raising `NoMethodError` when column names can't be resolved in CTEs. The issue stems from `order_column` returning an `Arel::Nodes::SqlLiteral` that lacks type information, so the query builder tried to type-cast something that doesn't exist. The solution skips type casting for CTE columns where type info isn't available anyway [2]. This is a surgical fix for anyone using modern Rails query patterns with window functions and temporary result sets. Separately, Rails hardened the helper method system for Ractor safety [3], following the same dup-add-freeze-reassign pattern established in recent concurrency work. The framework also stripped unnecessary complexity from content string handling [4], removing a nil interpolation workaround now optimized away in Ruby 3.1. Over in the asset pipeline, tailwindcss-rails 4.6.0 [5] shipped with signal forwarding for the watch task [6], eliminating the orphaned `tailwindcss` CLI processes that plague foreman users. When foreman sends SIGTERM to the watch task, it now traps INT and TERM, forwards them to the spawned child, and waits for cleanup instead of abandoning zombie processes. This is the fix for anyone who's had to manually kill tailwindcss watchers mid-development.

Action items

→ Upgrade rails to pick up in_order_of CTE fix if you use complex queries with temporary result sets rails/rails [plan]
→ Update tailwindcss-rails to 4.6.0 if you use foreman in development to stop orphaned watchers rails/tailwindcss-rails [plan]
→ Monitor Rails main for Ractor safety improvements as concurrency patterns stabilize rails/rails [monitor]

References

[1] Merge pull request #57758 from viralpraxis/fix-in-order-of-raising-on-cte rails/rails
[2] Fix `in_order_of` raising on CTEs ↗ rails/rails
[3] Make AbstractController::Helper.helper_method ractor safe ↗ rails/rails
[4] Simplify PRE_CONTENT_STRING hash ↗ rails/rails
[5] v4.6.0 ↗ rails/tailwindcss-rails
[6] Forward stop signals to tailwindcss watcher ↗ rails/tailwindcss-rails

Quick answers

What shipped in Rails on June 18, 2026?: Rails patched a `in_order_of` crash when querying Common Table Expressions, while tailwindcss-rails 4.6.0 finally kills zombie watchers that plague foreman-based development. In total, 7 commits, 5 pull requests, and 1 releases landed.
Who contributed to Rails on June 18, 2026?: 4 developers shipped this update, including viralpraxis, andrewn617, skipkayhil, and jordan-brough.
What were the notable Rails updates?: Merge pull request #57758 from viralpraxis/fix-in-order-of-raising-on-cte, Fix `in_order_of` raising on CTEs, and Make AbstractController::Helper.helper_method ractor safe.

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 2 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 3 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

@rails 4 days ago

SOLID QUEUE 1.5.0 SHIPS WITH CRITICAL CONCURRENCY FIXES

Solid Queue v1.5.0 lands three separate fixes for a production bug that corrupts semaphore counts and lets concurrency-limited jobs run wild.

ruby 45 shipped 1-min read

Elsewhere on the wire

AI Agents about 21 hours ago

CLINE SHIPS FIVE CRITICAL AGENT FIXES AFTER END-TO-END TESTING BLITZ

Saoudrizwan just landed a cascade of fixes that prevent the agent loop from running wild, stop file reads from resolving to the wrong directory, and plug the compaction pipeline.

ai-agents 16 shipped 2-min read

Local LLMs about 21 hours ago

LLAMA.CPP SHIPS MINIMAX-M3 SPARSE ATTENTION, VLLM UNLOCKS HETEROGENEOUS PREFILL-DECODE

The inference stack gets a new model architecture and a fundamental shift in how prefill and decode can run on different hardware configurations.

+10

llms 125 shipped 1-min read

@CachyOS about 21 hours ago

GLIBC 2.43 REBUILD SHIPS, INSTALLER JUMPS TO C++26

CachyOS pushed glibc 2.43 through the pipeline while the CLI installer upgraded its C++ standard to C++26, signaling a major refresh across core infrastructure.

infra 97 shipped 1-min read

Elixir & Phoenix about 21 hours ago

ECTO FIXES SUBQUERY PLANNING IN JOINS, ELIXIR PATCHES IEX PARSING

Ecto's query planner now handles subqueries correctly in interpolated join filters, while Elixir fixes a syntax error that broke 'not in' as a continuation operator in IEx.