FastRuby.ioYou do not have to freeze feature work to upgrade Rails... 🤷
Go one minor version at a time, because there are simply too many changes between minors to leap safely. .
Ruby/Rails signal-to-noise is rough these days...
Our newsletter reduces all the noise: release notes that affect your app, security patches, upgrade strategies.
Planning a Rails upgrade usually starts with a blank page and A LOT of guesswork!
We built a free tool that generates an upgrade roadmap for you, either generic across versions or customized by connecting your GitHub repo.
It runs on OpenAI models that do not keep or learn from your data.
Generic plans list every possible deprecation, so you still filter what applies, but it beats starting from zero.
Check it out: https://go.fastruby.io/hrw
Long-running branches get a bad reputation, but on a big Rails upgrade they are often unavoidable...
The trick is keeping them lean: merge backward-compatible changes back to `main`, dual boot with `next_rails` so both versions run side by side, and sync `main` into the branch often so divergence never snowballs.
Branch protection plus CI on every PR keeps the merge honest.
Valid Eval needed Rails 7.1 and Ruby 3.4 to stay competitive on government contracts.
We upgraded their stack, hit 2-5x speedups on key endpoints, and resolved a Rails upgrade bug across 15-20 views in days, not weeks. Security improvements were a side effect, not an afterthought.
OmbuLabs.aiEvery Rails upgrade we ran shaped a tool. Then every tool got open-sourced!
Check out some of our favorite #OSS projects: claude-code_rails-upgrade-skill, dual-boot-skill, the whole claude-skills marketplace.
Extracting every Rails deprecation warning from source via tree-sitter ASTs beats brittle regex.
It handles 5 message formats and both deprecation APIs (the legacy ActiveSupport::Deprecation.warn and the modern Class.deprecator.warn)
Our playbook for fixing a broken test suite during a Rails upgrade: errors before failures, model tests first, batch the rest by root cause. Dual booting old vs new Rails makes diagnosis a lot faster. https://go.fastruby.io/87y #RailsUpgrade #RubyOnRails #Testing #LegacyCode
WNB.rbMeet Jill Klang!
Jill is an engineer on Shopify’s Ruby & Rails Infrastructure team who helps teams move large, legacy apps forward with confidence. In her talk, she’ll share a clear, repeatable playbook for planning, executing, and de‑risking upgrades on Rails Edge. You’ll also learn how small, focused open source contributions today can make tomorrow’s upgrade smoother for everyone.
Join us Tuesday, Oct 28 at 1PM ET. Link in bio.
💸 Don’t have $100,000 to upgrade your #Ruby application? Neither do we!
Check out our monthly, fixed-cost, top-notch upgrade plan (starting at $2,000/month) 🚀
