How we upgrade a Rails application

A Rails upgrade isn't a leap: it's a series of small steps, each one verifiable and reversible.

  1. Assessment

    We review Ruby and Rails versions, dependencies, test coverage and use of deprecated features. The result is a report with the version path, the risks and an estimate.

  2. Safety net

    Before touching anything, we make sure the critical flows are covered by tests that run in continuous integration. If they're missing, we write them.

  3. One version at a time

    We move version by version, skipping none, and clear the deprecation warnings first. The application can run on the current version and the next one at the same time, so your team keeps shipping features while we move forward.

  4. Dependencies

    We update every gem and replace the ones that are no longer maintained. Ruby is upgraded at the pace each Rails version needs.

  5. Rollout

    Every step goes through a staging environment and reaches production gradually, with monitoring and a rollback plan.

  6. Handover

    We adopt the new version's defaults, document what was done and leave a plan to keep the application up to date.

Is your Rails application falling behind?

Tell us which version it runs on and we'll tell you how to bring it up to date.

Let's talk about your project