When is Rails 8.2 coming out
Rails does not announce release dates. There is no public roadmap with a quarter on it, the core team has never committed to a cadence, and every confident date you find for a Rails minor was somebody reading the same tea leaves this page reads.
What there is instead is a complete public record of what has already happened, and it is worth more than a guess. Everything below was read from the RubyGems API on 2026-10-12.
First, it is not out
$ curl -s https://rubygems.org/api/v1/versions/rails.json \
| ruby -rjson -e 'puts JSON.parse($stdin.read).map { _1["number"] }.grep(/^8\.2/)'
Nothing. Across all 521 published versions of the rails gem, 347 stable and 174 prereleases,
there is no 8.2 of any kind.
The thing that confuses people here is that rails/rails main already calls itself 8.2.0.alpha.
That is not a release candidate and not a signal. Main carries the next version's alpha label from
the moment the previous minor branches, which on this timeline has been true for most of a year.
What main actually contains is a real question with a real answer, and it is in
Rails 8.2, read from the source.
The record
Every minor since 6.0, with the gap from the one before it:
| Version | Released | Days since previous minor |
|---|---|---|
| 6.0.0 | 2019-08-16 | 494 |
| 6.1.0 | 2020-12-09 | 481 |
| 7.0.0 | 2021-12-15 | 371 |
| 7.1.0 | 2023-10-05 | 659 |
| 7.2.0 | 2024-08-09 | 309 |
| 8.0.0 | 2024-11-07 | 90 |
| 8.1.0 | 2025-10-22 | 349 |
Median 371 days, mean 393, range 90 to 659.
355 days have passed since 8.1.0. That puts today just inside the median gap, which is the strongest thing anybody can honestly say: on history alone, 8.2 is due around now and has not slipped by any standard this table sets.
The row to look at twice is 8.0.0. Rails went 659 days between 7.1 and 7.2, then 90 days from 7.2 to 8.0, a major version, three months after the minor before it. Whatever rule you think governs this cadence, that row breaks it. Rails ships when the work is done and the timing of Rails World, which falls in September, appears to matter more than any interval.
The signal that actually moves first
Minors do not arrive unannounced. They arrive behind a beta, and the beta is public on RubyGems the day it is cut.
8.1.0.beta1 2025-09-04
8.1.0.rc1 2025-10-15
8.1.0 2025-10-22
48 days from the first beta to the final release, with a release candidate a week out.
No 8.2 prerelease exists today. That is the one genuinely useful inference on this page: if the last cycle is any guide, the final is at least six or seven weeks behind a beta that has not appeared, so 8.2 is not landing this month. Set a watch on that endpoint rather than on a date.
$ curl -s https://rubygems.org/api/v1/versions/rails.json \
| ruby -rjson -e 'puts JSON.parse($stdin.read).map { _1["number"] }.grep(/^8\.2/)'
An empty answer is the status quo. The first line it prints will be 8.2.0.beta1, and the clock
starts there.
Meanwhile the 8.1 line is alive
A quiet main does not mean a quiet project, and the patch stream says where the effort is:
| Version | Published |
|---|---|
| 8.1.0 | 2025-10-22 |
| 8.1.1 | 2025-10-28 |
| 8.1.2 | 2026-01-08 |
| 8.1.2.1 | 2026-03-23 |
| 8.1.3 | 2026-03-24 |
| 8.1.3.1 | 2026-07-29 |
| 8.1.4 | 2026-09-24 |
Four releases in 2026 so far, the most recent three weeks ago. The newest publication on any Rails
line at all is 7.2.4, also 2026-09-24, which is a maintained branch two minors back still getting
attention on the same day.
If you are waiting on 8.2 to pick up a fix, check whether it has already been backported. On this record it probably has.
What to do while you wait
Nothing about 8.2 should block an upgrade, and the ordering is the same as it always is.
Be on the latest 8.1 patch. 8.1.4, today. The jump from the current minor to the next one is
the cheapest it will ever be from the top of the previous line, and every one of the patches above
is a fix somebody already needed.
Flip the new defaults before the version arrives, not after. The eleven behaviours behind
config.load_defaults 8.2 are not gated on the release. They exist in main now, each one is a
separate line you can turn on in config/initializers/new_framework_defaults_8_2.rb, and turning
them on one at a time on 8.1 is how an upgrade stops being an event. That file and what each line
does are covered in Rails 8.2, read from the source.
Do not plan around a date. There isn't one. If a release matters to your quarter, the thing to watch is the prerelease endpoint above, which will tell you about seven weeks ahead, and that is as much notice as the project has ever given anybody.
What this page does not cover
No prediction. There is deliberately no date in this article, because the only inputs available are seven historical gaps with a 569 day spread and the absence of a beta, and neither supports one.
Nothing here was read from rails/rails itself. The release branch, the milestone list and the
commit traffic on main would all say more about how close 8.2 is than the RubyGems index does, and
none of them were looked at. The 8.2.0.alpha version string is quoted from a previous article
rather than re-read today.
The RubyGems API's own quirks are relevant and are covered separately: the counts move between two
reads, the response is cached well past its own max-age, and created_at for anything before
2009 is the import date rather than a release date. That is in
How many times has Rails been downloaded. The release dates used in
this article are all from 2019 onward, where the field is reliable.
Comments
No comments yet. Be the first.