rails-upgrade-7-to-8

What problem does it solve?

Upgrading a Rails application from 7.x to 8.0 introduces breaking changes from new default stack components (Solid Queue, Propshaft, built-in authentication) and accumulated deprecations across minor versions. Teams often rush the upgrade, adopting all new defaults at once and breaking existing functionality, or skip minor version hops and pile up unfixable deprecation warnings.

Core Features & Use Cases

• Staged dual-boot upgrade workflow: Guides teams through the 7.0 → 7.1 → 7.2 → 8.0 hop sequence using next_rails to avoid breaking the main branch.
• Optional default adoption guidance: Provides clear decision frameworks for adopting new Rails 8 defaults (Solid Queue, Solid Cache, Propshaft, built-in auth) only after the version upgrade is stable, avoiding unnecessary rework.
• Use Case: A team running Rails 7.0 with Sidekiq, Devise, and a custom Sprockets asset pipeline can use this skill to upgrade to Rails 8.0 in 3 separate PRs, keeping their existing tooling intact until they are ready to adopt new defaults.

Quick Start

Use the rails-upgrade-7-to-8 skill to plan and execute a staged upgrade of your Rails 7.x application to Rails 8.0, including dual-boot configuration and deprecation remediation steps.