Rails Upgrade Latest

5. Resolve breakages and deprecations:

• Fix boot/runtime errors and then failing tests.
• Address deprecation warnings proactively to reduce next-step breakage.
• Upgrade config, initializers, autoloading, Active Storage, and Action Cable settings when required by the guide/release notes.

6. Run mandatory quality gates:

• Run bundle exec rspec; do not finish while any spec fails.
• Run bundle exec rubocop; do not finish while offenses remain.
• If either fails, fix issues and rerun both commands until both are green in the same state.

7. Finalize:

• Summarize changed files, migration notes, and any required follow-up tasks.
• Call out remaining risk areas explicitly (for example: untested paths or temporarily retained legacy defaults).

Required Behaviors

• Prefer smallest safe change set per version step over big-bang upgrades.
• Never skip release notes for the exact target version.
• Never claim completion unless both bundle exec rspec and bundle exec rubocop pass.
• If a project cannot run one of those commands, state the blocker and the exact missing prerequisite.

Reference Map

• references/upgrade-workflow.md: Rails-guide-aligned checklist, command sequence, and per-version validation points.