Who contributed to Rails on June 27, 2026?

3 developers shipped this update, including adrianna-chang-shopify, etiennebarrie, and pascalbetz.

What were the notable Rails updates?

Report PostgreSQL default timestamp/time precision as 6, Merge pull request #57872 from 55728/fix-invert-drop-virtual-table-positional, and Merge pull request #57871 from 55728/fix-remove-check-constraint-if-exists-expression.

@rails

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

github ↗

Pick a date

Topics: Ruby Full archive →

The Wire · Showcase

RAILS FIXES TIMESTAMP PRECISION AND MIGRATION REVERSIBILITY IN OVERNIGHT PUSH

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

3 people shipped this

adrianna-chang-shopify @adrianna-chang-shopify 1 cited

etiennebarrie @etiennebarrie 1 cited

pascalbetz @pascalbetz 1 cited

PostgreSQL timestamp columns now report their actual microsecond precision to Active Record, fixing a long-standing type casting inconsistency that could silently corrupt datetime handling across your stack.

The Rails team shipped three critical fixes that tighten database schema handling. First, Rails now correctly reports PostgreSQL's default timestamp/time precision as 6 (microseconds) [1], ensuring type casting normalizes timestamps consistently with what's actually stored. This matters because bare timestamp columns without explicit precision were being misreported, causing data integrity issues on read. Second, the migration system now properly handles reversibility for `drop_virtual_table` [2] and `remove_check_constraint` with the `if_exists` flag [3], so your down migrations won't fail on already-missing objects. In parallel, the docs got fixed: month_field and week_field examples were incorrectly showing type="date" [4], and select helpers were documenting impossible boolean attributes. Over in the concurrency department, ActiveSupport JSON encoders are now Ractor-shareable [5], clearing the way for safer concurrent encoding in Ruby 3.2+. Meanwhile, solid_cable got a stability patch: reconnect attempts now reset properly after successful database access [6], preventing cascading failures on temporary connection hiccups.

Action items

→ Review timestamp handling in datetime-heavy models and add tests for microsecond precision consistency rails/rails [plan]
→ Update any custom migrations using drop_virtual_table or remove_check_constraint to verify reversibility rails/rails [plan]
→ If running solid_cable, upgrade to pick up the reconnect_attempt reset fix rails/solid_cable [monitor]

References

[1] Report PostgreSQL default timestamp/time precision as 6 ↗ rails/rails
[2] Merge pull request #57872 from 55728/fix-invert-drop-virtual-table-positional rails/rails
[3] Merge pull request #57871 from 55728/fix-remove-check-constraint-if-exists-expression rails/rails
[4] Fix incorrect RDoc examples in ActionView form helpers [ci skip] rails/rails
[5] Make ActiveSupport::JSON encoders Ractor-shareable ↗ rails/rails
[6] Reset reconnect_attempt after successfuly accessing the DB. ↗ rails/solid_cable

Quick answers

What shipped in Rails on June 27, 2026?: PostgreSQL timestamp columns now report their actual microsecond precision to Active Record, fixing a long-standing type casting inconsistency that could silently corrupt datetime handling across your stack. In total, 22 commits and 13 pull requests landed.
Who contributed to Rails on June 27, 2026?: 3 developers shipped this update, including adrianna-chang-shopify, etiennebarrie, and pascalbetz.
What were the notable Rails updates?: Report PostgreSQL default timestamp/time precision as 6, Merge pull request #57872 from 55728/fix-invert-drop-virtual-table-positional, and Merge pull request #57871 from 55728/fix-remove-check-constraint-if-exists-expression.

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.