$ the-wire · showcase
Rails documents what reload actually resets, docs server pins Ruby 3.3.5
By RepoJournal · Filed · About Rails · Composed from the cited sources · methodology
1 person shipped this
A quiet day in rails/rails: the only merged work is a documentation clarification from Xavier Noria that pins down which state <code>reload</code> touches and which state it leaves alone, plus a Ruby 3.3.5 floor on the docs server.
Clarify scope of record reloading rails/rails
Noria's reword states that <code>reload</code> reloads attribute values and resets what Active Record controls, while any custom state on the record survives. That matters when a record caches values from an external service: the cached state is still there after a reload, and Noria notes you may get unexpected state in a test suite because of it.
Clarify scope of record reloading rails/rails
The change landed on main as part of the same documentation effort; there is no change to reload behavior itself, only to what the docs promise.
Merge pull request #58929 from rails/fxn/reload rails/rails
The merge commit that carried the reload documentation clarification into the tree.
Tweak a bit last doc edits rails/rails
A follow-up tweak to the preceding doc edits, cleaning up wording rather than adding new claims.
Ruby 3.3.4 -> 3.3.5 rails/rails-docs-server
The docs server moved from Ruby 3.3.4 to 3.3.5 out of necessity: Bundler reported "Could not find compatible versions" because the releaser gem requires Ruby >= 3.3.5.
