Who contributed to Rails on June 12, 2026?

2 developers shipped this update, including Edouard-chin and paracycle.

What were the notable Rails updates?

Reject attribute names that shadow CurrentAttributes methods, Introduce ActiveRecord::PrimaryKey value object for composite keys, and Introduce a new mechanism for applications to prepare for ractor safety.

@rails

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

github ↗

Pick a date

Topics: Ruby Full archive →

The Wire · Showcase

Rails hardens CurrentAttributes isolation, ships composite key value object

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

2 people shipped this

Edouard-chin @Edouard-chin 1 cited

paracycle @paracycle 1 cited

A critical fix prevents request state leakage in CurrentAttributes, while new composite key infrastructure consolidates scattered logic across the ORM.

Rails plugged a dangerous isolation hole in CurrentAttributes by rejecting :attributes as a declared attribute name [1]. Declaring an attribute with that name shadowed the internal reader/writer that reset() relies on, causing per-request state to leak across requests. The INVALID_ATTRIBUTE_NAMES denylist had caught most problematic names, but :attributes slipped through. This ships as a safeguard against subtle, production-grade state corruption bugs.

On the composite key front, Rails introduced ActiveRecord::PrimaryKey, a value object that ends the scattered `is_a?(Array)` checks littering finders, relations, associations, and counter cache logic [2]. Each site was rebuilding where hashes, type casts, and primary key inference independently. The value object encapsulates the single-column vs. composite distinction behind a clean interface (`composite?`, `col`), with follow-up commits applying it across remaining branches [4] [5].

Rails is also laying groundwork for Ractor safety by introducing a preparation mechanism for applications to make their procs shareable [3]. This addresses edge cases where application code prevents Rails from automatically making procs Ractor-safe, which will matter as concurrency tooling matures.

Action items

→ Review CurrentAttributes usage if you declare custom attributes; reject :attributes as a name rails/rails [plan]
→ Track composite key value object refactor if you maintain composite key code; the interface is now stable rails/rails [monitor]
→ Audit route resolution procs for Ractor isolation if you target concurrent Ruby releases rails/rails [monitor]

References

[1] Reject attribute names that shadow CurrentAttributes methods rails/rails
[2] Introduce ActiveRecord::PrimaryKey value object for composite keys rails/rails
[3] Introduce a new mechanism for applications to prepare for ractor safety ↗ rails/rails
[4] Refactor Composite Primary Key implementation by using polymorphism ↗ rails/rails
[5] Apply PrimaryKey value object to remaining composite-key branches rails/rails

Quick answers

What shipped in Rails on June 12, 2026?: A critical fix prevents request state leakage in CurrentAttributes, while new composite key infrastructure consolidates scattered logic across the ORM. In total, 25 commits and 10 pull requests landed.
Who contributed to Rails on June 12, 2026?: 2 developers shipped this update, including Edouard-chin and paracycle.
What were the notable Rails updates?: Reject attribute names that shadow CurrentAttributes methods, Introduce ActiveRecord::PrimaryKey value object for composite keys, and Introduce a new mechanism for applications to prepare for ractor safety.

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.