All Articles

How to Prioritize Which CVEs to Fix First

You run bundler-audit against your app, and the list is longer than you have time for, with a good share of it flagged HIGH or CRITICAL. There are too many to patch at once, and every one looks urgent. Sorting by severity doesn’t help when everything is already labeled critical, and a list where everything is top priority gives you no priority at all.

In this post, you’ll learn how to combine three public scoring signals, CVSS, the CISA KEV catalog, and EPSS, to narrow your application’s dependency advisories down to a list, and then how to check whether each flaw on that list is actually reachable in your codebase. Think of it as the systematic version of picking CVEs by hand, which is what we did in Don’t Just Upgrade Rails: 7 CVEs to Patch opens a new window .

Read more of How to Prioritize Which CVEs to Fix First opens a new window

SF Ruby '26: Ruby's Best Years Are Ahead

On November 10, I was in the audience at SFJAZZ when Irina Nazarova opens a new window opened SF Ruby 2026 opens a new window . Irina is the CEO of Evil Martians, and for the last three years she has been interviewing founders who are building new companies on Ruby and Rails.

A month ago I wrote about DHH’s Rails World keynote opens a new window , and I ended that post wanting to hear more about the future of Rails from the people building on it.

Irina’s keynote was that talk.

She opened with a video message from Garry Tan, President and CEO of Y Combinator, who couldn’t make it in person. He said one line that Irina kept coming back to for the rest of the hour:

Ruby’s best years might be ahead of us.

I left the room agreeing with him. Here is why.

Read more of SF Ruby '26: Ruby's Best Years Are Ahead opens a new window

Four AI Stack Risks bundler-audit Won't Flag

Many of the Ruby on Rails apps we work on now have an AI layer of some kind. Sometimes it’s a single RubyLLM chat in a background job, sometimes it’s an MCP client wired into a support tool, and on most teams there’s a coding agent running in somebody’s editor. That layer gets the same security process as the rest of the app, which usually means bundler-audit opens a new window in CI and a Ruby upgrade when somebody gets to it.

The last few weeks produced four separate problems in that layer. None of them has an advisory against a Ruby gem, so a dependency scanner stays green for all four. Two come from reading the source of ruby_llm-mcp, a community MCP client gem, one is a version constraint, and one is a compromised editor extension that isn’t a Ruby problem at all, but runs on the machines where our Rails credentials live.

In this article, we’ll go through each one: what happened, how to tell whether it affects your app, and what to do about it.

Read more of Four AI Stack Risks bundler-audit Won't Flag opens a new window

What We Check Before Migrating Off Heroku

We recently moved a client’s Ruby on Rails app off Heroku: a Rails API with Sidekiq workers and several services around it. Before we changed anything, we spent about a week on discovery. We had a kickoff call with the client’s team on a Monday, and then two of us paired for the rest of the week to map the infrastructure and draft a migration plan.

Nothing about that app followed one pattern. Its services were deployed in different ways, and some of the things that mattered most for the migration, like the tools outside Heroku that read from the database and the service that promoted code to production, didn’t show up in the Heroku dashboard at all.

In this article, you will learn what we inventory before moving an app off Heroku, where to look beyond what Heroku shows you, and what our own discovery missed. Almost none of it depends on where you are going: it applies whether your target is Render, Fly.io opens a new window , AWS, or something else.

Read more of What We Check Before Migrating Off Heroku opens a new window

Making AI Agents Safe to Retry

Over in the OmbuLabs.ai blog, our post on the ReAct pattern in Ruby opens a new window walked through building an agent that reasons about a task, calls tools, and acts on the results, all inside a single Ruby script. That’s fine for a command-line experiment. It’s a different story once that same agent needs to run inside a Rails app, triggered by a web request, where a multi-step reasoning loop can easily take longer than any request should stay open.

The obvious fix is to move the agent into a background job. Sidekiq already handles work that takes a while, so an agent’s loop of thinking, searching, and acting should fit right in. It does, mostly, but a job’s retry semantics were built around retrying a database write, not a chain of API calls that has real, sometimes irreversible, side effects.

In this article, you’ll learn why an agent’s reasoning loop doesn’t survive a naive move into a background job, how to make its side effects idempotent against Sidekiq retries, and how to stream its progress to the user while it runs.

Read more of Making AI Agents Safe to Retry opens a new window

Bootstrap 4 to 5, One Controller at a Time

You’ve decided your Ruby on Rails app needs to move from Bootstrap 4 to Bootstrap 5. Bootstrap 4 is end of life opens a new window and no longer receives bug fixes or security updates. Maybe you also want to get jQuery out of your front end, or maybe a component you need only exists in version 5. The catch is that Bootstrap 5 renames classes and data attributes, and that touches many of the views in the app. In a large application, changing all of them in a single pull request is hard to review, hard to test, and hard to roll back.

We recently borrowed the idea behind the Dual-Boot technique opens a new window , running two versions of a dependency side by side, for something other than Rails: Bootstrap itself. Instead of upgrading everything at once, we kept both versions in the app and moved one controller at a time, for many of the same reasons that you might upgrade Rails in increments opens a new window . In this article, you will learn how to run Bootstrap 4 and 5 side by side in one Rails app, how to pick the version per controller with a layout, and how to sequence the migration into small pull requests.

Read more of Bootstrap 4 to 5, One Controller at a Time opens a new window

Can You Remove DatabaseCleaner?

DatabaseCleaner was a very popular gem that helped you keep a clean database between tests. However, newer versions of Rails removed the need for this tool for most cases. Even so, many applications that always used it still use it to this day. Let’s talk about what it does, why it was needed, and why you probably don’t need it anymore, and when you still might.

Read more of Can You Remove DatabaseCleaner? opens a new window

Rails World '26: Rails in the Agentic Era

I was in the audience at Rails World 2026 for Ryan Sherlock’s talk, “Shipping is your heartbeat: Rails in the agentic era.” Ryan is Senior Director of Engineering at Fin opens a new window , the company formerly known as Intercom, and he shared how a very large Rails monolith gets code from a pull request into production.

And it is large. The app is 15 years old, has about 5 million lines of code, and gets deployed more than 200 times a day, with roughly 5 minutes between merging a pull request and seeing it live. In a post on X after the talk opens a new window , Ryan added that they run about 230,000 tests (25,000 of them added in August alone) and ship a new backend every two to three minutes.

Read more of Rails World '26: Rails in the Agentic Era opens a new window

DHH, AI, and the Future of Rails

I was in the audience in Austin when DHH opened Rails World 2026. The conference tagline was “Shaping the future of Ruby on Rails,” so I walked in expecting to hear about the future of Rails.

That’s not quite what happened.

The opening keynote opens a new window was almost entirely about AI agents. DHH told the room that 37signals has gone “pencils down” on writing code by hand, that HEY is moving to native apps with a Rust backend, and that he has retired as a professional programmer.

The next day, he sat down with Matz and Jeremy Daer for Ruby, Rails, and the future of programming opens a new window , which went even further down the same path.

I’ll recap both sessions, share where I disagree with them, and explain why I’m still excited about where Rails is going. There is a lot going on behind the scenes to make Rails faster and more secure, and to give the view layer some much-needed attention.

Read more of DHH, AI, and the Future of Rails opens a new window

Rails World '26: Hot Cell for Active Storage

I was in the audience at Rails World 2026 when Mike Dalessio, a Rails Core team member who joined earlier this year, put up a slide that said “You are not worried enough (probably).”

He had good reasons to say it.

This summer, Mike handled CVE-2026-66066 opens a new window , an Active Storage vulnerability that let a crafted image upload read files from the server, including your application’s secrets.

His talk, Hot Cell: Securing Active Storage in the age of AI opens a new window , was half post-mortem and half proposal: if we can’t stop image libraries from being vulnerable, maybe we can stop their vulnerabilities from reaching our secrets.

In this article, you will learn what that CVE actually meant, why patching image libraries is no longer enough, how Hot Cell sandboxes Active Storage, and whether you can use it in your Rails application today.

Read more of Rails World '26: Hot Cell for Active Storage opens a new window

Rails World '26: The As-If Rule, Ractors & AI

I was in the audience at Rails World 2026 when Aaron Patterson (tenderlove) kicked off the closing keynote. Aaron opened with a well-worn line: “the purpose of a system is what it does.” He wasn’t satisfied with it. The purpose of a system, he argued, is what it does for whoever is observing it.

Hand an old Nokia 3310 to someone who has never seen a cell phone before, and they might use it as a hammer. In that moment, to that person, it is a hammer. What a system does depends on who’s watching.

That distinction has a name in compiler design: The as-if rule.

In this post, we’ll walk through what the as-if rule means for Ruby’s compiler, where Ractors push it right up to its edges, and how the same idea explains a real RubyGems.org security incident that played out earlier this year.

Read more of Rails World '26: The As-If Rule, Ractors & AI opens a new window

Rails World '26: The RubyGems Compact Index

I was in the audience at Rails World 2026 for Jenny Shen’s talk on the RubyGems Compact Index, the last technical talk before the closing keynote. Jenny is a Senior Developer at Shopify and a RubyGems.org opens a new window maintainer, and she opened by asking the room who had heard of the compact index before. Not many hands went up, which was kind of the point: it’s a piece of infrastructure that handles tens of millions of requests a day, and most Rubyists never think about it.

Read more of Rails World '26: The RubyGems Compact Index opens a new window

Rails World '26: Herb and ReActionView

I watched Marco Roth’s talk at Rails World 2026, and it left me excited about where the Rails view layer is headed.

Marco has spent the last couple of years building Herb, an HTML-aware ERB parser that is on its way into Rails 8.2 core, and at Rails World he showed what he is building on top of it: A project called ReActionView opens a new window .

Read more of Rails World '26: Herb and ReActionView opens a new window

Run the Rails Agent Benchmark Yourself

Last month the Rails Foundation published something the Ruby on Rails community had not seen before: a leaderboard of coding agents scored on real Rails work. The first Agents on Rails report opens a new window topped out at 92% in the Accuracy column for the best model tested, which is roughly what you would expect from a field of frontier models. The Rails API recall opens a new window column tells a different story: it shows the share of runs where the model reached for the Rails API that a task was built around, instead of hand-rolling its own version. In that first report it ran from 8% to 35%, and a follow-up published on September 2 opens a new window moved the top of the range to 41%.

Those results describe Writebook opens a new window , the application the benchmark runs against. They do not describe your application. On August 24 the Rails team open sourced lemans opens a new window , the harness behind every number they have published, which means you no longer have to take the leaderboard’s word for anything.

In this article, you will learn what lemans measures, how to build a small bench you can run on your own machine, and how to prove that bench is worth trusting before you spend anything on it.

Read more of Run the Rails Agent Benchmark Yourself opens a new window

Rails World '26: Lexxy for Action Text

I was in the audience at Rails World 2026 for Jorge Manrubia’s talk on Lexxy, a new rich text editor for Action Text. Jorge is a Principal Programmer at 37signals, and if you’ve used Active Record Encryption, you’ve used something he built.

Jorge explained why 37signals built a new editor, what Lexxy adds, and how the work opens Action Text to other editors beyond Trix, the editor that’s shipped with Action Text since day one.

In this post, we’ll walk through why Trix became a maintenance burden, why 37signals picked Meta’s Lexical framework over the more obvious open source contenders, and what Lexxy actually does differently inside Action Text.

Read more of Rails World '26: Lexxy for Action Text opens a new window