Ruby & Rails Versioning at Scale
summary
Shopify automates Rails upgrades across 300+ Ruby services by combining an upgrade calendar with tooling that actually performs steps not just proposes them A bespoke rails_upgrade gem runs idempotent upgrade steps commits atomic changes and regenerates RBI via Tapioca while a web app Solid Track uses GitHub Actions to open PRs Dependabot RuboCop and Bundler get patched to use the Ruby version file Results include 90 apps moved to 7.0.8 in a week 80 percent to 7.1 in months and company Rails variants collapsing from ~20 to two minor versions
AI-written summary · about
chapters (14)
- 0:00Welcome
- 1:05Rails upgrades feel harder
- 3:12Rails versioning basics
- 7:01Challenges at Shopify scale
- 8:26Psychological barriers
- 12:16Upgrade calendar
- 14:43Security and stability benefits
- 17:34Scaling Rails upgrades
- 19:00Rails upgrade gem
- 23:16Solid Track web app
- 27:12Scaling Ruby upgrades
- 29:02Ruby version challenges
- 33:14Developer feedback
- 33:59Key takeaways
related talks
33mUpgrading a big application to Rails 5
22mRiding Rails for decades
29mUpgrading Rails at Scale
28mUpgrading Rails: The Non-Technical Parts
21mRails Upgrade Mastery: Best Practices for Large-Scale Enterprise Applications
35mChanging the wheels on the bus at 80 mph: Upgrading to Rails 3
27mScaling Ruby Applications: Challenges, Solutions and Best Practices
54mKeynote: The Success of Ruby on Rails