Ten years of Rails upgrades
summary
History at Clio shows upgrades slow because dependencies rot and custom hacks proliferate so the practical fixes matter: a small Ruby script bundle_report lists oldest and incompatible gems, a lightweight deprecation tracker ties deprecations to tests and blocks new ones, and a simple dual-boot wrapper bin/next boots the app under the next Rails. Results are concrete: 33 gems removed, 27 updated, deprecations reduced to zero and about 90% of next‑Rails failures fixed.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 2:02Two Rails upgrades
- 8:55Code decays
- 10:53Dependencies
- 16:05Disconnect
- 18:01Upgrade
- 23:26Outlaw
- 26:54Dual Boot
related talks
28mUpgrading Rails: The Non-Technical Parts
33mUpgrading a big application to Rails 5
46mAncient Rails
22mRiding Rails for decades
32mZero downtime Rails upgrades
36mRuby & Rails Versioning at Scale
21mRails Upgrade Mastery: Best Practices for Large-Scale Enterprise Applications
36mRuby & Rails Versioning at Scale