$ the-wire · showcase
RAILS LOCKS DOWN INFLECTION RULES, CEMENTS RACTOR SAFETY
By RepoJournal · Filed · About Rails · Composed from the cited sources · methodology
2 people shipped this
Rails is freezing inflection rules after boot, closing a mutation vector that could introduce hard-to-trace bugs and clearing the path to Ractor compatibility across the framework.
The inflection freeze [1] is the heavy lift this cycle. Rails now prevents mutations to inflection rules post-boot, eliminating a non-deterministic codepath that could silently change how the framework converts between table names, class names, and constants. This fixes a real foot-gun: someone mutating inflections in a callback or initializer would create bugs that surface randomly in tests but not production, or vice versa. The patch also unblocks Ractor safety by removing a mutex interaction that would have blocked multi-threaded execution. Related, ActionView's LookupContext is now initialized early [2], avoiding mutex contention when enable_reloading is false and clearing another Ractor blocker. On the routing front, Rails fixed a trailing-slash edge case [3] where blank paths with query parameters were getting mangled. The permissions policy system now correctly applies source mappings to dynamic sources [4], addressing a gap in CSP handling. These are surgical fixes across core systems that improve determinism and threading safety without breaking existing code.
Action items
- → Review custom inflection code in initializers and ensure mutations happen before boot rails/rails [plan]
- → Monitor upgrade path if you're using ActionView context manipulation post-boot rails/rails [monitor]
References
- [1] Freeze the inflection rules after the app boots ↗ rails/rails
- [2] Initialize ActionView::LookupContext.view_context_class early ↗ rails/rails
- [3] Merge pull request #57938 from 55728/fix-path-for-trailing-slash-frozen rails/rails ↗
- [4] Merge pull request #57939 from 55728/fix-permissions-policy-dynamic-source-mappings ↗ rails/rails
