Ryz Labs/Migrations/Rails 7.2 end of life
Migrations

Rails 7.2 End of Life: Upgrade Plan to Rails 8.1

Rails 7.2 stopped getting security fixes on August 9, 2026. Here is how to find exposure, what 8.0 and 8.1 remove, and a staged path to Rails 8.1.

Rails 7.2 reached end of life on August 9, 2026, the end of its security window under the Rails maintenance policy. It no longer receives security fixes from the project. The recommended target is Rails 8.1, which the policy lists with security fixes until October 10, 2027, reached by stepping through 8.0 one minor at a time on a maintained Ruby, with new framework defaults turned on gradually and the 7.2 build kept deployable until 8.1 is proven.

Key dates

Rails gives each series bug fixes for one year and security fixes for two years after its first release. The live maintenance page now lists only 8.1 and 8.0; the 7.2 dates come from earlier published versions of that same page, which carried 7.2 until September 24, 2026.

VersionReleasedEnd of life (security fixes end)Status on November 21, 2026
Rails 7.2August 9, 2024August 9, 2026 (bug fixes ended August 9, 2025)End of life
Rails 8.0November 7, 2024November 7, 2026 (bug fixes ended May 7, 2026)Listed security date has passed
Rails 8.1October 22, 2025October 10, 2027 (bug fixes listed until October 10, 2026)Supported for security, recommended target

Dates are from the official Rails maintenance policy and the rubygems.org release dates, checked November 21, 2026. Two notes. First, the live page still shows the 8.0 security date of November 7, 2026, which has passed, so treat 8.0 as a stepping stone, not a destination. Second, no Rails 8.2 is listed yet, which is one more reason to land on 8.1 and stay current on its patch releases.

Ruby has its own calendar, and it matters here because Rails sets a floor. According to Ruby's branch page, Ruby 3.2 reached end of life on April 1, 2026, Ruby 3.3 is expected to reach it on March 31, 2027, and Ruby 3.4 and 4.0 have no end date announced.

What end of life means for your systems

From August 9, 2026, a security issue found in Action Pack, Active Record, Active Storage or any other Rails framework gets a patch on supported series only. Your 7.2 app keeps working, but every new advisory against it becomes a code change you own instead of a gem bump you install. Bug fixes for 7.2 had already stopped a year earlier.

The Ruby layer often makes this worse. Rails 7.2 only requires Ruby 3.1.0 or newer, so many 7.2 apps still run on Ruby 3.1 or 3.2, both past end of life on ruby-lang.org. An app in that state has two unsupported layers, and fixing one does not fix the other.

For compliance, the relevant control is vulnerability handling. Under SOC 2, criterion CC7.1 expects a company to detect and manage vulnerabilities, and a framework series with no upstream patches leaves you answering each Rails advisory by hand. We wrote up how that criterion applies to code in SOC 2 for AI-assisted codebases. Buyers' vendor reviews also tend to ask which framework and language versions you run; a reply of Rails 7.2 on Ruby 3.1 now invites a follow-up question about your upgrade date.

Find your exposure

The main monolith is rarely the only Rails 7.2 app you have. For each location below, write down the app, its Rails and Ruby versions, and who owns it.

Want the dates without building a spreadsheet? Drop a Gemfile.lock, a .ruby-version file or a Dockerfile into the EOL deadline radar, which is free, and you get back a dated report showing where Rails and Ruby stand against their official calendars.

What changes in the upgrade

The Upgrading Ruby on Rails guide lists no itemized steps for 7.2 to 8.0 beyond the release notes, and one for 8.0 to 8.1. The real work is in what each release removes. Below are the items that tend to matter most when the starting point is 7.2.

Ruby first, and Ruby separately

The guide says "Rails 8.0 and 8.1 require Ruby 3.2.0 or newer" and advises upgrading Ruby on its own: "Upgrade to the latest Ruby you can first, and then upgrade Rails." Because 3.2 is past end of life, the floor Rails sets is not a good target. Pick a maintained Ruby above it, run your suite on it while still on Rails 7.2, and ship that change alone. That isolates Ruby breakage from Rails breakage, which is the whole point.

Settings removed in Rails 8.0

The Rails 8.0 release notes remove several options that 7.2 only warned about, including config.read_encrypted_secrets, action_controller.allow_deprecated_parameters_hash_equality, active_record.commit_transaction_on_non_local_return, active_job.use_big_decimal_serializer, ActiveSupport::ProxyObject, and passing nil to the model: argument of form_with. Old apps tend to carry these in config files copied forward for years, and a removed setting can stop the app from booting. Search config/ for each name before you bump the gem.

New defaults in 8.0 worth testing deliberately

Rails 8.0 sets Regexp.timeout to one second by default as a guard against ReDoS. That is a good change, but a slow, legitimate regular expression in a parser or importer can now raise where it used to finish. Run long imports and report jobs on 8.0 in staging. The release also adds params.expect as a safer alternative to params.require(...).permit(...); adopting it is optional, but it is a cheap hardening step while you are touching controllers.

Propshaft, Solid Queue and Kamal: optional for an upgrade

Rails 8.0 makes Propshaft the default asset pipeline in place of Sprockets, and adds Solid Cache, Solid Queue and Solid Cable as database-backed options for roles that often run on Redis, plus Kamal 2 and Thruster for deployment. The upgrade guide does not list switching to any of them as a required step for an existing app. Keep the upgrade and the infrastructure change apart: upgrade Rails on your current asset pipeline and job backend, then evaluate each new piece as its own project.

Rails 8.1 finishes what 8.0 deprecated

Several items deprecated in 8.0 are gone in Rails 8.1: drawing routes with multiple paths, the Active Storage Azure service, the SQLite3 retries option, Benchmark.ms, bin/rake stats, and the old enqueue_after_transaction_commit values. Semicolons as query string separators are also removed, which can affect old clients or webhooks that send them. This chain is why the guide says to go one minor at a time: 8.0 tells you what 8.1 will remove, and skipping straight to 8.1 throws away those warnings.

New deprecations to burn down on 8.1

Rails 8.1 deprecates order-dependent finders such as first without an order, the built-in sidekiq adapter in favor of the one in the sidekiq gem, String#mb_chars, ActiveSupport::Configurable and config.active_support.to_time_preserves_timezone. None of these break today, but the first-without-order warning tends to fire across a large codebase and points at real bugs where results depend on database row order.

schema.rb columns sort alphabetically

The one itemized 8.0 to 8.1 change in the upgrade guide: Active Record now sorts table columns alphabetically in schema.rb. Expect one large diff the first time you run a migration on 8.1. Commit it alone with a clear message so reviewers do not hunt for real schema changes in it. Teams that need exact column order can use structure.sql.

The upgrade plan

A 7.2 app is close to current, so this is a two-step version climb, not a modernization. If you also have apps on Rails 6.x or older, or a monolith that needs boundaries, that is a bigger job covered in our legacy Rails to Rails 8.1 runbook.

Inventory and baseline

List every app, engine and internal gem with its Rails and Ruby version. Move each app to the latest 7.2 patch, as the guide recommends, and get the suite green with deprecation warnings visible in test output. Record response times, job throughput and error rates per app as the baseline you will compare against.

Compatibility testing

Ship the Ruby upgrade first on Rails 7.2. Then follow the guide's steps for each hop: change the Rails version in the Gemfile, run bundle update rails, update JavaScript packages (and run bin/rails javascript:install if you use jsbundling-rails), run bin/rails app:update, and review every diff it proposes. Setting THOR_DIFF and THOR_MERGE lets you use your own diff tool. Fix deprecations to zero on 8.0 before starting the 8.0 to 8.1 hop. Upgrade internal gems and engines before the apps that consume them.

Staged rollout

Deploy each hop to staging, then to a canary or a share of traffic. Background jobs deserve their own canary: run a small set of workers on the new version against the real queue and watch retries and failures. Leave config.load_defaults on the old version at first. The update task writes config/initializers/new_framework_defaults_X_Y.rb; turn its settings on one or a few at a time over several deploys.

Cutover and rollback

Hold on to the prior build so you can redeploy it until 8.1 has shipped several ordinary releases without incident. Reverting is quick only while migrations remain backward compatible, so separate schema changes from the framework bump and avoid dropping columns the old version still reads. Once all new defaults are enabled and stable, delete the defaults file and set config.load_defaults to the new version, as the guide describes.

Cleanup

Remove the old Ruby from images and CI, drop leftover compatibility settings, retire any dual-version CI jobs, and add a check so new apps cannot be generated on an end-of-life Rails or Ruby. Rails 8.1's Local CI, declared in config/ci.rb and run with bin/ci, is one way to make that check part of every developer's run.

PhaseGoalKey techniqueExit criteria
Inventory and baselineKnow every Rails 7.2 app and its RubyGrep Gemfile.lock, gemspecs, .ruby-version and DockerfilesEvery app on the latest 7.2 patch, suite green, warnings visible
Compatibility testingGreen suite on 8.0, then 8.1Ruby upgrade shipped alone; bin/rails app:update per hop; internal gems firstZero deprecation warnings on 8.0 before the 8.1 hop
Staged rolloutProve each hop in productionWeb canary plus a separate job-worker canary; defaults file enabled graduallyWeb and worker canaries hold to the 7.2 numbers
Cutover and rollbackEvery app serving on 8.1, reversiblePrevious build kept deployable; backward-compatible migrationsStable through a release cycle; load_defaults flipped
CleanupRetire Rails 7.2 and old Ruby for goodRemove old Ruby and settings; add a version check to CIInventory shows no Rails 7.2 or end-of-life Ruby

Risk matrix

RiskLikelihoodImpactMitigationEarly warning
Internal gem or engine pinned to Rails 7.2 blocks bundle updateHighMediumUpgrade shared gems first and release them before the appsBundler resolution errors naming railties
App fails to boot on a removed 8.0 config optionMediumHighSearch config/ for every removed setting before bumpingNoMethodError or unknown config errors at boot in CI
Ruby upgrade breaks a native-extension gemMediumHighShip Ruby alone on Rails 7.2; update or replace the gemCompile failures during bundle install in the new image
Regexp.timeout raises in a long-running parser or importLowMediumRun heavy imports in staging on 8.0; fix or scope the expressionRegexp timeout errors in job logs
Job backend change slips into the upgradeMediumHighKeep the current backend; plan Solid Queue as a separate projectQueue config files changing in the upgrade branch
Clients sending semicolon query separators break on 8.1LowMediumCheck access logs for semicolons in query strings before the hopParameters missing on specific webhook or legacy client requests
Order-dependent first calls return different rowsMediumMediumBurn down the 8.1 deprecation warnings by adding explicit ordersDeprecation volume in test and production logs

Typical team shape

Three skills carry a Rails 7.2 to 8.1 climb. Someone senior decides the hop order and keeps the app list honest. Rails engineers work through each app:update diff and drive deprecation counts to zero. A platform person rebuilds Ruby images, CI jobs and the worker canary. With many small apps, several engineers can run hops in parallel once the shared gems are released. Many teams begin with a pod of 3 to 5 senior engineers (a tech lead plus engineers), and a full pod is about seven. Ryz engineers work on your team, reporting to your leads. You can bring in Ruby on Rails developers for the app work and DevOps engineers for images and CI. When a hosting change rides along with the upgrade, read the Heroku to AWS runbook first.

Ryz engineers on your team start from $7,000 per month (our published range is $7,000–$15,000 per engineer per month, mostly mid-level to senior), quoted per team. Once you say go, engineers can typically start in under two weeks. Honest view: a handful of well-tested apps and a team with spare capacity can do this without us. If that is not your situation, scope your team and we will put a plan and names in front of you.

Related

FAQ

Is Rails 7.2 still safe to run after end of life?

Your app will keep serving requests. What changed on August 9, 2026 is that the Rails core team stopped publishing security releases for 7.2, so a new advisory becomes your patch to write. Many 7.2 apps also run on Ruby 3.1 or 3.2, which are past end of life too. Treat it as a short bridge while you upgrade.

Which version should we upgrade to?

Rails 8.1, which the maintenance policy lists with security fixes until October 10, 2027. Step through 8.0 on the way, but do not stop there, because its listed security date has passed. Run it on a maintained Ruby above the 3.2.0 floor that Rails 8.1 requires.

How long does the upgrade take?

The drivers are test coverage, the number of internal gems and engines that pin Rails, your starting Ruby, native-extension gems, removed settings lingering in config, and discipline about keeping infrastructure changes out of the branch. A well-tested app already on a current Ruby is two careful hops; a fleet of small untested apps is more work.

Can we pay for extended support?

Neither the Rails maintenance policy nor the upgrading guide mentions a paid support tier for 7.2. Some hosting platforms and commercial vendors sell backported patches; check with yours on scope and end date, and use any such option only to buy time for the upgrade.

What does it cost to bring in engineers?

Rates begin at $7,000 a month per engineer and run to $15,000 for most of our mid-level and senior people, with leads quoted per team. Multiply headcount by months by rate for the total. Before anything starts, you see a written plan, a price and the engineers who would do it.

Questions we didn't answer? Email info@ryzlabs.com.

Thanks — your message has been sent. We’ll get back to you soon.

Something went wrong while sending your message. Please try again or email info@ryzlabs.com.

Explore Ryz Labs

Software development servicesAI development companyIndustriesStaff augmentationAI pod teamsNearshore software developmentHire engineers by roleEngineer ratesGuidesBuyer guidesCase studiesHow we vet engineers

Ryz Labs

Senior engineers on your team. AI pod teams that ship.

Tell us what you're building. You get a scoped plan, a price and the names of the people who would do the work.

  • Only the top 1% of tens of thousands interviewed make it
  • On US business hours, including New York hours
  • Trusted by Fortune 500 engineering teams

Tell us who you need

A Ryz partner replies with a scoped team plan.

Start a conversation →

Prefer to talk? Book a 15-min call →