#railsupgrade — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #railsupgrade, aggregated by home.social.
-
Internal gem breaking on a Ruby or Rails upgrade? First question: is the error coming from your code or an external dependency. That answer changes the fix completely, sometimes it's a patch, sometimes you're forking someone else's gem just to keep moving. Test hard before you ship it.
-
Internal gem breaking on a Ruby or Rails upgrade? First question: is the error coming from your code or an external dependency. That answer changes the fix completely, sometimes it's a patch, sometimes you're forking someone else's gem just to keep moving. Test hard before you ship it.
-
Your app is ready for the next Rails version and then your own internal gem blocks the whole thing. First question to answer: is the error coming from your gem's code or from one of its dependencies? If a dependency has no compatible release yet, forking and patching is a legitimate move. Sometimes a broad gemspec constraint just needs bundle update parent_gem.
-
Your app is ready for the next Rails version and then your own internal gem blocks the whole thing. First question to answer: is the error coming from your gem's code or from one of its dependencies? If a dependency has no compatible release yet, forking and patching is a legitimate move. Sometimes a broad gemspec constraint just needs bundle update parent_gem.
-
bundler-audit is necessary and not sufficient. CVE-2026-66066 hits default Rails 7.0+ setups using vips, and patching the gem is only half of it. You also need libvips 8.13 or newer, and gem-level scanning never sees the system library.
https://go.fastruby.io/agj
#RailsSecurity #Ruby #RailsUpgrade -
bundler-audit is necessary and not sufficient. CVE-2026-66066 hits default Rails 7.0+ setups using vips, and patching the gem is only half of it. You also need libvips 8.13 or newer, and gem-level scanning never sees the system library.
https://go.fastruby.io/agj
#RailsSecurity #Ruby #RailsUpgrade -
After 100+ Rails upgrade projects and 30,000+ engineering hours, the pattern is clear: complexity drives cost more than app size, and test coverage drives predictability. A 6.1 to 7.0 jump runs roughly $60k to $135k; older jumps cost multiples of that. https://go.fastruby.io/3uk #RailsUpgrade #TechnicalDebt
-
After 100+ Rails upgrade projects and 30,000+ engineering hours, the pattern is clear: complexity drives cost more than app size, and test coverage drives predictability. A 6.1 to 7.0 jump runs roughly $60k to $135k; older jumps cost multiples of that. https://go.fastruby.io/3uk #RailsUpgrade #TechnicalDebt
-
Still on sass-rails or LibSass? Both are dead upstream. The good news: your SCSS survives. sass-migrator handles the dependency rewrites, and moving @import to @use finally kills global namespace pollution, so color: variables.$brand-color instead of guessing where $brand-color came from. https://go.fastruby.io/igo #Rails #Sass #RailsUpgrade
-
Still on sass-rails or LibSass? Both are dead upstream. The good news: your SCSS survives. sass-migrator handles the dependency rewrites, and moving @import to @use finally kills global namespace pollution, so color: variables.$brand-color instead of guessing where $brand-color came from. https://go.fastruby.io/igo #Rails #Sass #RailsUpgrade
-
Low test coverage is not a reason to skip a Rails upgrade. Define the critical path (signup, payments), wire up Sentry or Honeybadger to catch what QA misses, and ship small revertable PRs. Risk management beats coverage perfection. https://go.fastruby.io/q3c #RailsUpgrade #TestCoverage #Ruby
-
Low test coverage is not a reason to skip a Rails upgrade. Define the critical path (signup, payments), wire up Sentry or Honeybadger to catch what QA misses, and ship small revertable PRs. Risk management beats coverage perfection. https://go.fastruby.io/q3c #RailsUpgrade #TestCoverage #Ruby
-
The quiet win in a Rails upgrade is not the version bump. For one government-contract SaaS it was Puma memory and response times improving across the platform under a steady monthly plan. Their team also told us we saved them three or four days on a bug they had been fighting alone. https://go.fastruby.io/l4s #RailsUpgrade #Puma
-
The quiet win in a Rails upgrade is not the version bump. For one government-contract SaaS it was Puma memory and response times improving across the platform under a steady monthly plan. Their team also told us we saved them three or four days on a bug they had been fighting alone. https://go.fastruby.io/l4s #RailsUpgrade #Puma
-
Nearly two years of staggered Rails upgrades across multiple apps, and the scoreboard for a 500-person publicly traded company: infrastructure costs down 5 to 10 percent, faster product development, and better engineer morale. Their words: more stable, moving faster, costs going down. https://go.fastruby.io/pf2 #RailsUpgrade #TechnicalDebt
-
Nearly two years of staggered Rails upgrades across multiple apps, and the scoreboard for a 500-person publicly traded company: infrastructure costs down 5 to 10 percent, faster product development, and better engineer morale. Their words: more stable, moving faster, costs going down. https://go.fastruby.io/pf2 #RailsUpgrade #TechnicalDebt
-
Inheriting a Rails app nobody on your team wrote? Go quantitative before qualitative. Run bin/rails stats to see its shape (one app we audited ran a 1:0.6 code-to-test ratio), skim the Gemfile and bin/setup, then dig into routes, models, and controllers. When grep fails, method(:name).source_location shows where a method really lives. A codebase reflects the team that built it. https://go.fastruby.io/skm #RubyOnRails #LegacyCode #RailsUpgrade
-
Inheriting a Rails app nobody on your team wrote? Go quantitative before qualitative. Run bin/rails stats to see its shape (one app we audited ran a 1:0.6 code-to-test ratio), skim the Gemfile and bin/setup, then dig into routes, models, and controllers. When grep fails, method(:name).source_location shows where a method really lives. A codebase reflects the team that built it. https://go.fastruby.io/skm #RubyOnRails #LegacyCode #RailsUpgrade
-
If you upgrade Rails apps, our Claude Code skills are open source and free to grab. The claude-skills marketplace bundles the FastRuby.io upgrade methodology, the rails-upgrade skill automates a lot of the modernization grind, and the dual-boot skill runs your app against two Rails versions at once using Bundler and next_rails. Tools we use every day.
https://www.ombulabs.ai/open-source?utm_source=mastodon&utm_medium=Organic&utm_campaign=EvergreenPromo&utm_content=Textonly&utm_term=ombu-open-source-mastodon-2026-07 #RailsUpgrade #ClaudeCode #OpenSource -
If you upgrade Rails apps, our Claude Code skills are open source and free to grab. The claude-skills marketplace bundles the FastRuby.io upgrade methodology, the rails-upgrade skill automates a lot of the modernization grind, and the dual-boot skill runs your app against two Rails versions at once using Bundler and next_rails. Tools we use every day.
https://www.ombulabs.ai/open-source?utm_source=mastodon&utm_medium=Organic&utm_campaign=EvergreenPromo&utm_content=Textonly&utm_term=ombu-open-source-mastodon-2026-07 #RailsUpgrade #ClaudeCode #OpenSource -
Before a Rails upgrade, guessing the scope is how projects blow past their timeline.
The `next_rails` gem runs bundle_report outdated and hands you the real number (one app came back at 156 of 218 gems behind, about 72%).
It also checks Ruby and Rails compatibility and groups your most common deprecation warnings so you can clear them systematically.
-
Before a Rails upgrade, guessing the scope is how projects blow past their timeline.
The `next_rails` gem runs bundle_report outdated and hands you the real number (one app came back at 156 of 218 gems behind, about 72%).
It also checks Ruby and Rails compatibility and groups your most common deprecation warnings so you can clear them systematically.
-
`next_rails` does way more than dual booting Ruby applications...
Point it at a stuck app and it tells you the hard truth: one project came back with 156 of 218 gems out of date, 72%.
It also finds the minimum #Ruby for your target #Rails and tracks deprecation warnings across test runs so nothing slips through your upgrade.
-
`next_rails` does way more than dual booting Ruby applications...
Point it at a stuck app and it tells you the hard truth: one project came back with 156 of 218 gems out of date, 72%.
It also finds the minimum #Ruby for your target #Rails and tracks deprecation warnings across test runs so nothing slips through your upgrade.
-
Rails apps rarely die because of a single incident.
They die in a thousand small frictions: slow deploys, flaky tests, gem updates nobody touches. The fix is steady, not heroic. 60,000+ hours of FastRuby upgrade work, distilled.
-
Rails apps rarely die because of a single incident.
They die in a thousand small frictions: slow deploys, flaky tests, gem updates nobody touches. The fix is steady, not heroic. 60,000+ hours of FastRuby upgrade work, distilled.
-
Rails upgrades without a roadmap turn 6-week jobs into 9-month projects...
Two devs, 10-15 days of analysis, 40-90 prioritized tasks, best and worst-case estimates. Get a roadmap based on real experience (60,000 dev/hours upgrading Ruby and Rails!)
-
Rails upgrades without a roadmap turn 6-week jobs into 9-month projects...
Two devs, 10-15 days of analysis, 40-90 prioritized tasks, best and worst-case estimates. Get a roadmap based on real experience (60,000 dev/hours upgrading Ruby and Rails!)
-
🚨 Running Ruby on a Heroku stack that no longer ships security updates is a quiet liability...
Heroku-20 already hit EOL, and Heroku-22 and 24 only support Ruby 3.1 and up. If your app is stuck below that, the stack migration and the Ruby bump have to happen together.
We mapped out which Ruby versions run on which stack so you can plan the jump.
-
🚨 Running Ruby on a Heroku stack that no longer ships security updates is a quiet liability...
Heroku-20 already hit EOL, and Heroku-22 and 24 only support Ruby 3.1 and up. If your app is stuck below that, the stack migration and the Ruby bump have to happen together.
We mapped out which Ruby versions run on which stack so you can plan the jump.
-
Rails 7.2 quietly raises the floor to Ruby 3.1, so the upgrade is really two upgrades.
The serialize signature also changed: it wants keyword args now, serialize :report, coder: JSON. Skip the old deprecation warnings and the app breaks on boot...
-
Rails 7.2 quietly raises the floor to Ruby 3.1, so the upgrade is really two upgrades.
The serialize signature also changed: it wants keyword args now, serialize :report, coder: JSON. Skip the old deprecation warnings and the app breaks on boot...
-
You 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. .
-
You 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.
-
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
-
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.
-
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.
-
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.
-
Every 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)
-
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)
-
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)
-
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)
-
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
-
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
-
Meet 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.
-
Meet 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.
-
Meet 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.
-
Meet 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) 🚀
-
💸 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) 🚀
-
💸 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) 🚀
-
💸 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) 🚀
-
This is exciting, a community member, Oscar has just dropped that they are working on upgrading Koalagator from Rails 7.0 to the latest Rails 8 release.
PR for 7.1.x to 7.2.2.x just landed.
https://github.com/koalagator/koalagator/pull/62
Other contributions welcome, have a look at our issues and drop us a line if you'd like to get involved.
#koalagator #calendaring #RubyOnRails #RailsUpgrade #dev #FOSS
-
This is exciting, a community member, Oscar has just dropped that they are working on upgrading Koalagator from Rails 7.0 to the latest Rails 8 release.
PR for 7.1.x to 7.2.2.x just landed.
https://github.com/koalagator/koalagator/pull/62
Other contributions welcome, have a look at our issues and drop us a line if you'd like to get involved.
#koalagator #calendaring #RubyOnRails #RailsUpgrade #dev #FOSS