Your monthly digest of Ruby Central updates, community highlights, and Ruby ecosystem news.
01 · From Ruby Central
Organization updates, program changes, announcements
Welcome to the Ruby Alliance
Ruby Central begins its new shift toward a more stable and brighter tomorrow with one of its new initiatives, The Ruby Alliance. The Ruby Alliance was first introduced to the public in April of this year, and this program immediately took root as conversations blossomed with interest from quite a few community leaders and companies.
Ruby Alliance in a Nutshell
This is a coalition of influential companies that want to see change in the Ruby ecosystem and serve as the foundation for the long-term impact of Ruby's perseverance and evolution into the future. This is a small group of founding companies that commit to a substantial amount of support for RubyGems and its infrastructure that many Ruby-dependent organizations rely on.
These are large commitments of $150,000+ in the form of either fiscal support and/or engineering contributions.
Welcoming our First Founders
Gusto, thoughtbot, and Shopify were eager and swift to be part of this movement and answered the call.
These companies have continuously invested back into the Ruby ecosystem — the same one that supports their teams and businesses every day. They bring experienced leadership, operational perspectives, and a strong commitment to supporting the long-term health of Ruby and the infrastructure we all depend upon.
Expanding the Open Source Team
We're excited to announce two additions to the Open Source team.
Dushan Karovich-Wynne
Security Engineer
Dushan Karovich-Wynne joins us as our Security Engineer, where he'll lead security efforts at RubyGems.org and contribute to our AI security scanning work sponsored by Alpha-Omega. Dushan brings deep experience across Linux, cloud, low-level systems, sandboxing, cryptography, and supply chain security, along with a background leading teams and operating large-scale production web systems. He's excited to step into his first role as a professional open source contributor. His philosophy: "Security engineered in from first principles, less is more, the secure path should also be the easy path." Welcome, Dushan!
Brian Tenggren
In-Kind Engineer · thoughtbot via Ruby Alliance
Brian Tenggren is starting the first rotation as an in-kind engineer from thoughtbot through the Ruby Alliance. Brian is helping push Organizations from beta toward general availability and move the RubyGems.org redesign forward. Having dedicated engineering capacity through the Alliance is a significant step for the team. It lets us build toward a real roadmap and make sustained progress on the work the community has been waiting for. Welcome, Brian!

July 14–16, Las Vegas
We're Coming Together at RubyConf 2026. Will You Be There?
It's wild how fast time moves nowadays. With everything happening in our daily lives, the constant flood of information, and the bewildering news cycle that seems to change by the hour, it's easy for things to slip through the cracks or get pushed aside to "deal with it later."
RubyConf 2026 has been in the works since last year, and the team is still working right up to the wire making adjustments to the program to ensure the Ruby community gets the best experience possible. When we committed to hosting this event, we couldn't have imagined the world we're living in today. We see it. We're feeling the shift in the tech industry, especially in the Ruby world. And we want to be open about something: running an event like this is costly, and we know so many of you, and so many across our industry, are navigating real uncertainty right now. Getting people together in person has never felt harder.
But that's exactly what RubyConf is for.
It's a space to feel seen and heard. To collaborate and connect with people who are figuring out the same things you are. To be part of one of the most welcoming communities in tech. And right now, we think showing up matters more than ever.
The Themes Say It All
Beautiful Ruby · Weird Ruby · Living with the Robots
Here's a mirror. These themes are a direct reflection of what we're all grappling with in the Ruby ecosystem right now. How do we keep building things that feel meaningful with AI in the mix? Are you still working without AI, and how are you navigating a workspace that increasingly seems to demand it? What strange, creative, exciting things are Rubyists making now? And how do we keep the human part of Ruby alive through all of it? These are the conversations happening at RubyConf 2026, and they're worth having in person.
You Are Not Alone In This
Remote work, economic pressure, the pace of AI… it can all make you feel like you're flying solo and isolated. At RubyConf, you're sitting in a room with people who get it. You can air your frustrations, find a new angle on a problem you've been stuck on, or get inspired to build something new.
And some of the best moments don't happen in the talks -- they happen in the late-night brainstorming, hacking, and workshopping of Community Day. Did you know RubyGems was conceptualized during exactly that kind of session at RubyConf what feels like forever ago? It's one of those facts that makes you stop and think about what a single conversation at the right moment can produce.
If you've never tried Community Day, Hack Spaces, or the workshops, we're inviting you to this year. Maybe they haven't felt relevant to your day-to-day work, or you've never had an easy entry point into open source collaboration. But it might be exactly the thing that reignites your excitement for programming and reminds you why you fell in love with Ruby in the first place.
This Year Is One Worth Showing Up For
Ruby Alliance leaders will be in the room discussing the future of Ruby in a big way. Steering Committees are launching. And the speaker lineup and honored guests this year make this one genuinely worth the trip. You'll have direct access to some of the OGs who built Ruby into what it is, alongside some of the sharpest new voices in the community.
If you've cared about where Ruby is headed, you'll want to have been in that room.
There's Still Time
A month out and still have time to get a ticket, book a room, and be part of something that will matter to this community. Be in the center of the exchange of ideas at one of the most pivotal moments for Ruby. How do we carry the beautiful, the weird, and the human parts of this language forward into whatever comes next? That conversation is happening at RubyConf 2026, and we'd love for you to be in it.
If price is standing between you and a ticket, reach out. We can't promise a solution for everyone, but we want the chance to try. Some of the most important perspectives in this community come from small consultancies, independent developers, open source maintainers, and early-stage startups. We don't want your voice missing from this room because of cost.
If you haven't booked your hotel yet, do it before June 19th (I know… a pretty quick turnaround). We negotiated a rate of $179++/night (roughly $242) -- well below the $330+ you'll pay after the block closes.
⏰ Hotel block closes June 19th
$179++/night (roughly $242) — well below the $330+ you'll pay after the block closes.
We can't wait to see you there.
02 · From the Engineering Team
Strengthening Security for the Ruby Ecosystem and What It Means for Maintainers
We're launching a team of Security Engineers in Residence, funded by Alpha-Omega, to find real vulnerabilities in the gems the Ruby community depends on most. If you've been following the reports on what Mythos is doing to vulnerability discovery, you know the landscape has shifted. Finding candidates is now cheap and fast, which means the bottleneck is verification and responsible disclosure, not detection. That's exactly what this program is built around. We're using the latest AI models to surface vulnerabilities, verify them, and responsibly engage with maintainers.
The work has already started. The team's first engagement produced a ReDoS vulnerability report to the Nokogiri maintainers, which they validated and fixed. We're building the playbook one careful engagement at a time. Read more about this new program in last week's announcement.
We're bringing the team to RubyConf.
On Day 2, members of the RubyGems Security team will be running a hands-on workshop, "From Scan to Fix: A Maintainer's Guide to Gem Security", that brings the lessons from this program directly to gem maintainers. You'll walk through the full lifecycle: what good security looks like for a gem, how to run a real scan, how to read the results, and how to triage and fix what you find. No prior security experience required.
Your gem could have a vulnerability sitting quietly in its codebase right now. Most maintainers aren't security engineers, and that's exactly who this workshop is for. If you maintain a gem, this is for you!
A Month of Closing Doors: Hardening the Ruby Supply Chain
This was a month of closing doors. The Ruby supply chain is a little harder to attack than it was in May, and most of what we shipped points that way.
Start with the one the community asked for most. Working alongside Shopify and the RubyGems team, we helped land cooldown in Bundler: a setting that holds new gem versions back for a few days after they are published, so a freshly compromised release cannot slip straight into your lockfile. You opt in with --cooldown 7, with bundle config set cooldown 7, or per source in your Gemfile. It mirrors what npm, pnpm, and Dependabot already offer, and it closes one of the most common supply-chain attack windows. This was a real collaboration between Shopify, Ruby Central, and the Ruby team, the kind of cross-company work that keeps the ecosystem healthy.
The same instinct ran through our work on RubyGems.org itself. Publishing a gem now requires a verified email address, and we have blocked anonymous and reserved TLD domains from signing up. We also disabled new registrations for a few days in mid-May while we worked through an incident. Small gates, but they shut real doors. The next one we are designing is the transparency log. This month it moved from idea to architecture: a verifiable, tamper-evident record of everything published to RubyGems.org. It is still early work, and we will share more as the design takes shape.
Not all of the month was about defense. We replaced RubyGems' old Molinillo dependency resolver with PubGrub, the same solver Bundler already uses. For years the two tools have resolved dependencies in slightly different ways. Now they share an engine. It is a large, unglamorous change, but it brings the long-running goal of unifying RubyGems and Bundler much closer. Alongside it, we shipped a batch of developer-experience improvements across the site.
03 · Quick Links & Upcoming Dates
Community Survey
2026 Ruby on Rails Community Survey — Deadline Soon
📊 The 2026 Ruby on Rails Community Survey is open, but deadline to submit is coming in FAST! The value of your input goes beyond each year of its release (9th year counting!). It just takes a few minutes of your time, so click on this link to get on it! There's only a few weeks left.
Board Updates
There's been a couple updates from the Ruby Central board of directors that you don't want to miss. Check out A New Chapter for Ruby Central, Modernizing Ruby Central's Bylaws and Officer Updates, & Governance: Expanding Participation in Ruby Central. More is coming down the pipeline from the board so make sure to stay updated at rubycentral.org/news.