Rails World 2026 is just 47 days away, and we have a few fun updates for you. If you haven’t already, you can grab your ticket here.

Now for the updates:

Matz is coming

Big news first: Matz is coming to Rails World 2026! He’ll sit down with DHH on day 2 for a fireside chat. It’s been two years since the last chat in Toronto, and so much has changed since then. We’re living in a different world, so we wanted to bring these two together on stage again to chat about Ruby, Rails, AI, and what the future holds for programming.

Attendees will be able to submit their questions beforehand. This session was made possible by the generous support of our Event Partner and sponsor, Shopify.

Full agenda is live, app is coming

The Rails World 2026 agenda is now live, so you can start planning. No worries if you get caught in the Hallway track, all sessions will be recorded and published within two weeks after the event, and the Opening Keynote will be livestreamed (more on that soon).

The Rails World app is also coming soon with more specific information for ticket-holders, so you can build your schedule, join the networking events, and stay on track.

Lightning talks are back

We’re only able to host a Lightning Track each year if a sponsor steps up, and this year two did: Sorcer and Judoscale. Each sponsor will host one day of Lightning Tracks in the breaks, so if you’re attending Rails World and have a talk in mind, the Lightning Track CFP is now open (ticket holders have been sent the link today so please check your inboxes). We’re looking for talks that inspire, teach, or spark a good debate, as long as you can deliver it in 5 to 10 minutes.

Thank you to our Platinum sponsors

AppSignal returns to Rails World as a Platinum Sponsor for the fourth year in a row! A long-time supporter of the Rails community and a member of the Rails Foundation, they’ve been part of the event since the very first Rails World in 2023.

We hear they’re bringing their sjoelbak tables, stroopwafels…and a load of new features to demo live in their booth.

We are pleased to welcome Procore as a first time sponsor at the Platinum level. They have generously offered to host the Rails at Scale Summit in their office in downtown Austin, and will co-sponsor the Closing Party with Shopify.

Procore has one of the largest Rails engineering teams in the world, and is a founding member of the Rails Foundation. We’re grateful to have their support at Rails World this year.

Thank you to both of our Platinum sponsors.

And so much more.

We have a lot more to share. Pair programming with Test Double, a board game night, live music, a great Closing Party (you know how Shopify throws a great one - this time they are joined by Procore), and even - yes, this is true - a little Texas style bull riding thanks to thoughbot. But all that and more will be in the next update.

For now, there’s still time to grab a ticket, join us in person, and discover it all for yourself.

Looking forward to meeting you soon!

The Rails World team

Matz is coming to Rails World 2026!
Ruby creator Yukihiro “Matz” Matsumoto is coming to Rails World 2026! He’ll join DHH, Aaron Patterson, Robby Russell, and the rest of the lineup in Austin this September, and the full conference agenda is now live. If you’ve been waiting to see what’s planned before grabbing a ticket or planning your schedule, now’s the time to take a look.

Fix pluck ignoring records assigned to a new record’s association
When the parent is unsaved, CollectionProxy#pluck read the null scope instead of in-memory records assigned to the association. After a regression that made ids delegate to pluck, both returned empty on a new record even with tags already assigned. pluck now reads the target records directly, so post.tags.pluck(:name) works before save — and ids follows along.

post = Post.new
post.tags = [Tag.create!(name: "ruby")]

post.tags.pluck(:name) # => ["ruby"]

Restore alias_attribute support in associations
Since Rails 4.2, association reads bypassed read_attribute for an internal fast path that skipped alias resolution. An alias_attribute on the owner’s foreign key or the target’s primary key was silently ignored; production apps worked around it by overriding _read_attribute itself. The performance gap has closed enough that associations honor aliases again.

class Post < ApplicationRecord
  alias_attribute :writer_id, :author_id
  belongs_to :author, foreign_key: :writer_id
end

post.author # reads FK via alias

Add query predicate hooks for Active Record types
Types can override transforms_query_predicates?, query_attribute, and query_value to customize how hash where predicates are built, without changing normal casting or serialization. That lets a MySQL UUID column stored in binary(16) accept readable UUID strings while rendering id = UUID_TO_BIN(?), or compare text through a normalized expression such as lower(name) = lower(?).

Fix search_field raising NameError when passed autosave: true
The documented autosave: true option never worked. SearchField#render called request directly, but tag objects have no access to the request, so every call raised NameError. It now reads from @template_object.request, so the reversed host lands in the autosave attribute as documented.

Fix continuation step cursors losing their type when a job is interrupted and resumed
Cursors were persisted as raw JSON, so a Date, Time, or GlobalID cursor came back as a String after interrupt and resume — breaking resume logic such as cursor.beginning_of_day. Cursors now serialize through ActiveJob::Arguments, the same path job arguments use, so the resumed step sees the same object it set before the interruption.

Allow prepared statements with query log tags
Query log tags previously forced prepared statements off. To keep them enabled alongside tagged queries, set config.active_record.disable_prepared_statements = false.

Show parameter markers for casted binds in SQL logs and EXPLAIN
Casted binds — plain arrays of values rather than ActiveModel::Attributes — logged as [[nil, "abcd"]] because there was no column name to pair with each value. They now show positional markers such as [["$1", "abcd"]], matching the $1 placeholder in the SQL.

Make CommandRecorder#record and #inverse_of private
These are internal APIs on ActiveRecord::Migration::CommandRecorder. Callers should use the public migration methods (create_table, add_column, and so on) directly, and combine them with revert to record inverted commands.

Make Mime types ractor-shareable
The Mime::Type registry is frozen at eager load, with types initialized as frozen objects. Registering or unregistering MIME types after application initialization is now deprecated — do that in an initializer instead.

Make the Action View dependency tracker registry Ractor-shareable
The dependency tracker registry can be shared across Ractors when the application opts in via Rails.application.ractorize!. Registering trackers after initialization is deprecated; wrap registration in ActiveSupport.on_load(:action_view) during boot instead.

A few deprecations landed this week:

Deprecate write_attribute(:id, value), positional #insert arguments, and passing binds to #insert, #update, and #delete

• write_attribute(:id, value) still routed to the primary key column. Use #id= on models whose primary key is not named id, matching the read-side deprecation from Rails 7.1.
• The positional pk, id_value, and sequence_name arguments to #insert are deprecated. Pass returning: in place of pk.
• The separate binds positional on #insert, #update, and #delete is deprecated. Pass Arel.sql("... ?", *binds) instead:

connection.insert(Arel.sql("INSERT INTO topics (title) VALUES (?)", "hello"))

You can view the whole list of changes here. We had 28 contributors to the Rails codebase this past week!

Until next time!

Subscribe to get these updates mailed to you.

Nominations are open for the 2026 Rails Luminary Awards
The Rails Foundation announced that nominations are open through August 21. The awards recognize people who have significantly advanced Rails for the benefit of the community.

Rails versions 7.2.3.2, 8.0.5.1, and 8.1.3.1 have been released
These security releases address a possible arbitrary file read and remote code execution vulnerability in Active Storage variant processing. Please upgrade as soon as possible.

Stop filtering i18n paths on initialize
Removes redundant path-globbing work during i18n initialization, cutting the load time from 400 ms to about 250 ms in one application with thousands of locale files.

Pass scheme to token authentication block in http_authentication
Token authentication methods now yield the authentication scheme as a normalized symbol to the authentication block. They also support requiring a specific scheme and returning the appropriate RFC 9110 challenge response.

Make lazy route loading thread-safe
Route drawing state moved from a boolean to a three-state flag guarded by a reentrant Monitor. This fixes a race where concurrent threads could dispatch requests against a half-drawn route set.

Deprecate TransactionState predicates, positional arguments to #insert, and binds passed to to_sql
A few cleanup deprecations landed this week:

• TransactionState#fully_committed?, #fully_rolledback?, #fully_completed?, and #nullify! are deprecated in favor of #committed?, #rolledback?, and #completed?.
• The positional pk, id_value, and sequence_name arguments to #insert are deprecated. Callers can use returning: in place of pk.
• The long-unused binds argument to to_sql is now deprecated instead of being silently ignored.

Extract table_name: as an explicit keyword argument in join table helpers
Migration join table helpers now accept table_name: as an explicit keyword argument instead of removing it from an options hash as a side effect.

Resolve the single best template without sorting the whole set
Template resolution now finds the best match in one pass and binds locals only for the winner instead of sorting and binding every candidate.

Support a single column name for #insert’s returning:
returning: now accepts a single column name and returns that column’s value directly. Previously it accepted only arrays, forcing callers to unwrap a one-element result.

Allow thread_mattr readers and writers to be used in a Ractor
Removes memoization of the per-thread key so thread_mattr readers and writers work safely in Ractors. Access remains in the nanosecond range despite the additional lookup.

Make controller middleware Ractor-safe
Uses a copy-on-write approach so controller middleware stacks can be shared safely across Ractors. A proxy refreezes the stack after direct method calls.

Refactor insert returning: handling to take QueryIntent directly
Insert RETURNING handling moved from raw SQL string manipulation to QueryIntent. Arel-based inserts can now set RETURNING directly on the AST.

Rename arel to arel_or_sql
Connection methods such as insert, update, delete, and explain accept either an Arel manager or a raw SQL string but used inconsistent parameter names. They now consistently use arel_or_sql.

Show parameter markers for casted binds in SQL logs and EXPLAIN
SQL logs and EXPLAIN output now show casted binds with positional markers such as $1 instead of [nil, value], making each value’s position clear.

You can view the whole list of changes here.
We had 25 contributors to the Rails codebase this past week!

Until next time!

Subscribe to get these updates mailed to you.

Rails Versions 7.2.3.2, 8.0.5.1, and 8.1.3.1 have been released!

These are security patches addressing 1 security issues:

• A possible arbitrary file read and remote code execution in Active Storage variant processing

We strongly recommend upgrading as soon as possible.

Older versions of Rails are unsupported, and users are recommended to upgrade to at least the 7.2 series. See our maintenance policy for details.

Here is more information about the security issue that these releases address:

• CVE-2026-66066 Possible arbitrary file read and remote code execution in Active Storage variant processing

SHA-256

If you’d like to verify that your gems are the same as the ones we’ve uploaded, please use these SHA-256 hashes.

ddc90d11dd88086d78ace03407fe3c2a3f5c8853c3c3046313db5ed823ef3312  pkg/activesupport-7.2.3.2.gem
3777c67cd8dd1560f30387523013dacb370a0a1cf532037410887819e4416927  pkg/activemodel-7.2.3.2.gem
e62d24ba7e5f820d24ed122eb9225491b0aaa8398778783b400067c3467285c7  pkg/activerecord-7.2.3.2.gem
42bfd966040c93271dfa9f3243d73c40aa0228108696f956e1f287f3b02edc01  pkg/actionview-7.2.3.2.gem
c1fbb1c4df0f2473ee064ab1412fc2a44c2c2ef337924c5ba3c7998c8529652b  pkg/actionpack-7.2.3.2.gem
b83fa070898911823f0c4cb8c0d1d25dabb5d00f18379d5b4fe01b84e173a93a  pkg/activejob-7.2.3.2.gem
45a6c326872867cdb28d2960d236c3c8fa4ff1198e9bc7ece4ddc3810b67b759  pkg/actionmailer-7.2.3.2.gem
04ffd91519942bae45f443bfc166308e6eb17870870cdfc1ca36bc95273c6b57  pkg/actioncable-7.2.3.2.gem
863cb4b21b83505555be2addb939fefb856ab05f6c6d24bab00d6f1a7e4edbfc  pkg/activestorage-7.2.3.2.gem
d19f6e98c5b630c391e14ce1a830f199f249bf3fd6208392f92d232a7a6d8ca5  pkg/actionmailbox-7.2.3.2.gem
19ab7e2a07ab976a5456a9aa98b93e1b899a7729b931ca1e9e01a3e8bd33f0b0  pkg/actiontext-7.2.3.2.gem
f626c6dfcc00a9f85b139619cfac4a648934c93e36fe5b9242184b9f45ffc29e  pkg/railties-7.2.3.2.gem
279290679f9005b0f79514f953a2af613f95de7baa94cbd87744c09122c1113c  pkg/rails-7.2.3.2.gem

329a4280c4fbcfcf338ae2cb9df28b0b14527929dba105e10b3604516d998710  pkg/activesupport-8.0.5.1.gem
559be32aa9c40db7a3ee0aef926d4508a9ebd22f96f7276c11326d21a7dff4a4  pkg/activemodel-8.0.5.1.gem
9252968fce404d75eb17092498a440d472167f2f8deee32b4658d6552b1eeea7  pkg/activerecord-8.0.5.1.gem
472a108b9cc2295c4ac3ff09b028045e619875801f48c556f0085210b9cb1440  pkg/actionview-8.0.5.1.gem
a5595c9d824d68884ddc4d3965ab78c897760d3752e190df7efe897371caa1eb  pkg/actionpack-8.0.5.1.gem
142407a21b6c3cbc6ddd92ca111ac18ea5c40298eb94d81845cd897a072a6880  pkg/activejob-8.0.5.1.gem
c3d2b3f96e1989ea25f51699786a97fcb2536eb7abfc2a667cb8f2376ec08403  pkg/actionmailer-8.0.5.1.gem
5adb700c605a7ef7628f87dc7a6da20cd5f0ceac782a59055c864ea51a77d7c7  pkg/actioncable-8.0.5.1.gem
239742932b2fdcf0ead175e0889dbd385a36da2168fd7bde023aaad88ef745f2  pkg/activestorage-8.0.5.1.gem
f8b72eadf53b3e285df8f2d1f6533012abf5a0a001180abe436aea3139eeaed6  pkg/actionmailbox-8.0.5.1.gem
370e90d35feb4313fc18ccef658776427d5bdd13126f266933b828a77e2125b2  pkg/actiontext-8.0.5.1.gem
da1958e1d9dab04691a2f8721b3ff7fab323715d37f103c19972dedfd644d5c7  pkg/railties-8.0.5.1.gem
c91cefbf38881876ddbe67b5e0246eb985d27d60c6bb1cd7034b4261de0ba495  pkg/rails-8.0.5.1.gem

85458765f25ea48b9019c46b6bb3fa5683197bf4280d9f06710a6e8d7a831376  pkg/activesupport-8.1.3.1.gem
99cc02ce2faec371d14440949d85787ebd23a907c9baef0a9d4bcd4d21888f88  pkg/activemodel-8.1.3.1.gem
0a2fb6c28f4938f6b013a3a549bec0a7e37d535f3dc8990e804bcc3258c0403b  pkg/activerecord-8.1.3.1.gem
2da68b8414c47b43bfbed1ce69c5afe1c04f78c267aacb5660a4cab5ca12cfb6  pkg/actionview-8.1.3.1.gem
974cb7154548e81f470b1b0f247b99cb38e87825899dca58610596e2817723d0  pkg/actionpack-8.1.3.1.gem
1c8dd275df930df40deecffec63d913a550a33fd94bd298f69721dd96939954a  pkg/activejob-8.1.3.1.gem
88ea441b28ff02a0c6c006468892642a3d9942affce9d294e81a74504aa5c43c  pkg/actionmailer-8.1.3.1.gem
e318528295c878a3efdfe25f0f2267c80cb7a76eba41bb5f64d44aa380a3d91b  pkg/actioncable-8.1.3.1.gem
f555254f387b1cffa499d2fd3115d12635eadc5b15206a8534316a67036163ef  pkg/activestorage-8.1.3.1.gem
5f704972097d843ade8e435e93694a1dac732b926df1717aceba1f3840082b1c  pkg/actionmailbox-8.1.3.1.gem
5da729d833d1a29cddb1eee938878e55e503d2613e00e735f5daf58c2ba98af2  pkg/actiontext-8.1.3.1.gem
2388a232579a00cefea4487de66c8553c3408c1300abdc6cf1799d86ffb04487  pkg/railties-8.1.3.1.gem
ccd11a36bfc171bf9c66d585d14c0ece91c0c9dde840aae60c0118d6f5c9c52a  pkg/rails-8.1.3.1.gem

The Rails Luminary Awards exist to celebrate those contributions, acknowledging those in the community who have significantly advanced Rails for the benefit of all, and the nominations for 2026 are now open.

If you know of someone who has consistently gone above and beyond to contribute to the framework, triaging bugs, improving performance, adding helpful features, etc. please nominate them below.

All nominations will be reviewed by Rails Core, and the final pick of Rails Luminaries will receive a trophy for their service, as well as a monetary award of $1,000.

Submit your 2026 Rails Luminary nomination here.

Fine print:

• Nominations for 2026 will remain open until August 21.
• Companies/corporations are not eligible for nomination.
• Past award recipients cannot be nominated again (names listed on the form).
• Self-nominations are not allowed; individuals must be nominated by others.
• Nominator personal information will be kept confidential and will not be shared publicly or with the nominee without explicit consent.

Documentation can only show you so much. Sometimes it’s better to just crack open the lid and go straight to the source to see how a real, production-quality Rails application is built. That’s harder to do well when there’s no curated starting point, so that’s what this library is meant to be.

Each entry links out to the full source so you can read the real thing: how the models are shaped, how a controller stays thin, how Turbo Streams actually get wired up, the full commit history, and all the small decisions made along the way.

This matters now, too, for a second audience: increasingly, people are looking for good examples to point their LLMs towards, so the code they produce is best set up for success. A small set of clean, current, production-quality examples gives both humans and models something solid to learn from.

So what’s in the library

We’re launching with three open source apps:

• Campfire - a complete, real-time group chat app.
• Writebook - a self-hosted platform for publishing books on the web.
• Fizzy - a Kanban board reimagined.

Wait, they’re all from…

Yes, so far they’re all apps built by 37signals. (That even caught DHH by surprise.)

These apps have often been pointed to as great examples to follow, and there’s no question that they follow Rails conventions to a T. Furthermore, seeing as we know they’re tried and tested, they were a great starting point for the library.

They’re now easier for you (and LLMs and anyone vibe-coding their way into the community for the first time) to find.

Big thank you to Rob Zolkos for designing and shipping this page for the Rails Foundation.

What’s next

This is a deliberately small library, and is not meant to be an exhaustive directory of open source Rails apps. We do plan to grow this library over time, but this will happen slowly and organically. We’ll announce when new applications are added.

You can find the library now on the Docs page, or go straight to /docs/reference-apps

Take a look and let us know what you think!

Send us your feedback at foundation@rubyonrails.org.

A Rails anniversary!
Today is the 22nd anniversary of the first public release of Ruby on Rails!

Learn from real, open-source Rails apps
On the Rails website, now you can find a small, hand-picked library of exemplary open-source apps worth reading to see how production-quality Rails is built today.

Update the JavaScript in Rails guide
The updated JavaScript in Rails guide is ready for community review!

Preserve sub-second precision when subtracting a DateTime from a Time
This pull request makes sure that sub-second precision is preserved when subtracting a DateTime from a Time. Time - DateTime converted both sides via to_f, so microsecond-level DateTime values lost precision. The difference is now computed from exact rational timestamps, matching Time.at(DateTime) and ActiveSupport::TimeWithZone - DateTime.

Deprecate RedisCacheStore::DEFAULT_REDIS_OPTIONS
The redis-client implementation no longer reads this constant. Pass timeout options to RedisCacheStore or a configured RedisClient instead.

Deprecate Cookies::HTTP_HEADER constant
You should migrate to Rack::SET_COOKIE from Cookies::HTTP_HEADER because it will be removed from future versions of Rails.

You can view the whole list of changes here.
We had 22 contributors to the Rails codebase this past week!

Until next time!

Subscribe to get these updates mailed to you.

Preserve sub-second precision when coercing a DateTime in Time.at
Fix Time.at to always return the correct number of milliseconds for a DateTime.

Accept Date and numeric inputs in relative_time_in_words
Normalize the argument in the same way distance_of_time_in_words does, so every documented input type works.

Respect a limit set on the relation in rails query
An Active Record expression that carries a limit like bin/rails query "Post.limit(5)" had its limit silently replaced by the pagination window returning up to a full page instead of the requested 5 rows.

Introduce ActionView::Helper::NavigationHelper
Methods like button_to and link_to now belong to this model (together with their siblings link_to_unless_current, link_to_unless, and link_to_if).

Honor if_not_exists: in SQLite3 add_check_constraint and add_foreign_key
The SQLite3 adapter never declared if_not_exists: so it fell into the bucked of unused options and a duplicate was added.

Read foreign key names from the schema on SQLite3
Before the change, on SQLite3, foreign_keys(table) returned nil for every foreign key’s name because the constraint name was never read from the table definition.

Support dumping schema_migrations in db/schema.rb
Provide a new flag that lets db/schema.rb include a dump of schema_migrations. The output will look like this:

ActiveRecord::Schema[8.2].define do
  ...
end

ActiveRecord::Schema.load_schema_migrations(__FILE__)
__END__
20260716101900
20260716112003
20260716130752
...

Fix MySQL POINT and MULTIPOINT columns misreported as integers
ActiveRecord was misreporting MySQL POINT and MULTIPOINT columns as integer columns instead of treating them as an unknown type like the other spatial types.

Convert Symbol keys in a transform_keys mapping
Ensures that the transform_keys method in HashWithIndifferentAccess transforms a hash that maps old keys to new ones even with Symbol keys.

Allow to access Controller#controller_path in a Ractor
Also note that AbstractController::Base#action_methods are now ractor safe.

Raise for empty shards on connected_to_all_shards
If an app isn’t sharded then connected_to_all_shards will now raise an error.

You can view the whole list of changes here.
We had 24 contributors to the Rails codebase this past week!

Until next time!

Subscribe to get these updates mailed to you.

The Rails Foundation is inviting RUG organizers from around the world to apply to be a Rails World MC
Ruby User Group organizers are a huge part of what makes the Ruby ecosystem special. They grow the community, create welcoming spaces, introduce speakers, keep events running smoothly, and make newcomers feel at home - all the things that make a great Rails World MC.

Add this_quarter? to Date/Time
It returns true if the date/time falls within the current quarter.

Date.current #=> Tue, 15 Feb 2000
Date.new(2000, 3, 31).this_quarter?  # => true
Date.new(2000, 4, 1).this_quarter?   # => false

Add ActiveJob::DeserializationError::RecordNotFound
Raised when argument deserialization fails because a referenced record could not be found, and not for any other reason.

Introduce ractorize!
Added Rails::Application#ractorize! method which prepares the application to be shared and then calls Ractor.make_shareable on it.

Fix ActionController::Live streams hanging on client disconnect
ActionController::Live::Buffer#abort cleared the streaming queue but never enqueued the terminator that each_chunk uses to exit, so a reader thread blocked in SizedQueue#pop was never woken and the request thread hung indefinitely.

Support endless and beginless ranges in number_field_tag / range_field_tag
Fixes raising RangeError when endless or beginless ranges passed.

Honor an explicit value: nil in color_field
Previously, passing value: nil was ignored and the field still pre-filled from the model’s stored color.

Deprecated the ActionController::Renderers::RENDERERS constant
This constant was for internal usage but had a documentation and wasn’t set as private. Applications that needs to add or remove renderers should be using the public API instead:

ActionController.add_renderer(:rtf) do
end

You can view the whole list of changes here.
We had 26 contributors to the Rails codebase this past week!

Until next time!

Subscribe to get these updates mailed to you.

Ruby User Groups (RUGs) are where people find their first Ruby friends, give their first talks, discover their next role, and become part of the community, and RUG organizers are a huge part of what makes the Ruby ecosystem special. They create welcoming spaces, introduce speakers, keep events running smoothly, and make newcomers feel at home — all the things that make a great Rails World MC too.

That’s why, this year, we’re inviting RUG organizers from around the world to apply to be a Rails World MC. If you’re comfortable in front of a crowd, enjoy bringing people together, and love the Ruby community, we’d love to hear from you.

As a Rails World MC, you’ll help guide attendees through the conference by:

• Opening and closing sessions.
• Introducing speakers.
• Keeping attendees informed throughout the day.
• Maintaining the pace and energy of the event.
• Being one of the welcoming faces of Rails World.

We’re looking for people who:

• Have organized a Ruby User Group anywhere in the world for at least one year.
• Love the Ruby and Rails community.
• Are warm, welcoming, and comfortable speaking to a crowd.
• Can keep the energy up while making speakers and attendees feel at home - for 2 full days.
• Are available to join us in Austin from September 22–25.

We’ll cover your hotel stay in Austin, and you’ll work closely with the Rails World production team to make sure you’re fully prepared before stepping onto the stage. You should also be a few preparation sessions in the weeks leading up to the event.

Interested?

If you’re a RUG organizer and this sounds like something you’d enjoy, we’d love to hear from you.

Fill out this form by July 19 and tell us a little about yourself, your Ruby User Group, and why you’d like to MC Rails World. Feel free to include links to any talks, meetup recordings, or event introductions you’ve done, but don’t worry if you don’t have any. We’re just as interested in your enthusiasm, your presence, and your love for the community.

We’ll be reviewing submissions over the coming weeks, and will let everyone know as soon as possible. We can’t wait to hear from you!

Questions? world@rubyonrails.org