$ the-wire · showcase
RAILS KILLS SLOW TEST TASKS, TIGHTENS CONSTANT MUTATION CHECKS
By RepoJournal · Filed · About Rails · Composed from the cited sources · methodology
2 people shipped this
Rails just removed its isolated test suite — a slow-running fixture that wasn't catching problems worth the CI overhead — and merged stricter linting rules to catch mutable constants before they ship.
The isolated test tasks [1] have been ripped out of the Rails build pipeline [3]. They ran slow, added complexity, and weren't surfacing bugs the rest of the test suite was missing anyway. That's the kind of pruning that keeps CI lean. Separately, Rails merged a new linting rule [2] that enforces immutable constants using the `literals` style — catching things like `CONSTANT = []` where mutation is possible. It's stricter, it's in production now, and existing Rails code will need to comply on next update. There's also a fix pending for MySQL adapters [4] around native database type freezing that connects to this constant hardening effort. All three changes ship together in the next Rails release and represent a push toward more predictable, harder-to-break code at the framework level.
Action items
- → Audit your constants for mutable literals (arrays, hashes) before upgrading Rails rails/rails [plan]
- → Remove any custom isolated test configurations from your CI setup rails/rails [monitor]
References
- [1] Remove isolated test tasks ↗ rails/rails
- [2] Enable `Style/MutableConstant` cop with `literals` style ↗ rails/rails
- [3] Merge pull request #177 from rails/remove-isolated ↗ rails/buildkite-config
- [4] Merge pull request #57333 from chaadow/patch-8 ↗ rails/rails
