Ruby 3.4 and 4.0 End-of-Life Timeline for Discourse Forum Hosting
Forum administrators who self-host Discourse must monitor the lifecycle of its underlying runtime environment to ensure community stability, platform performance, and server protection. Because Discourse depends on Ruby, tracking upstream runtime milestones allows administrators to plan upgrades systematically rather than reacting in haste when an environment stops receiving maintenance. Upstream development schedules provide clear visibility into active support phases and retirement dates. Examining these scheduled deadlines helps forum managers coordinate server maintenance windows, test dependencies, and preserve uninterrupted service for community members.
December 2024: Ruby 3.4 Launch and Active Patching
The timeline for cycle 3.4 officially began on 2024-12-24 with its initial public release. For self-hosted Discourse communities, tracking this branch is essential when managing base images and server packages. Across its maintenance lifespan, the release progressed through multiple updates, arriving at latest version 3.4.12 on 2026-10-23. According to endoflife.date Ruby release data, cycle 3.4 records an lts status of false, indicating that administrators should not anticipate an extended long-term support phase beyond the standard maintenance window. Keeping abreast of these minor versions ensures forum servers receive necessary patches, which community hosts can review alongside our overview of forum software server requirements.
December 2025: Ruby 4.0 Establishes the Next Horizon
Marking a major progression in the runtime ecosystem, cycle 4.0 debuted on 2025-12-25. This milestone set a new baseline for server environments preparing their application stacks for future software revisions. By 2026-10-22, maintenance for this major cycle advanced to latest version 4.0.9. Identical to the prior version branch, cycle 4.0 maintains an lts designation of false. Community administrators configuring modern hosting stacks must account for these continuous point revisions from upstream maintainers. Adapting server configurations to track active point releases keeps discussion boards responsive and operating smoothly.
March 2028: Retirement Milestone for Ruby 3.4
Every software release branch eventually reaches a scheduled conclusion when routine bug fixes and vulnerability patches cease. For forum servers operating on cycle 3.4, the official end-of-life date is set for 2028-03-31. When this milestone arrives, upstream maintainers will no longer produce security corrections or code updates for this line. Operating Discourse on an unsupported runtime creates unnecessary exposure for community databases, sessions, and server infrastructure. Preparing upgrade paths well before this cutoff is a core principle of sound forum admin security, ensuring that public-facing discussion boards never run obsolete server dependencies.
March 2029: End of Life for Ruby 4.0
The final target on the current hosting roadmap is the scheduled retirement of cycle 4.0, with an end-of-life date set for 2029-03-31. Community founders and hosting teams can use this date to establish multi-year planning cycles for their server stacks. Running forum software past a runtime retirement date leaves the hosting environment without critical fixes, exposing the server to unaddressed bugs. Reviewing the scheduled support timelines documented by endoflife.date Ruby lifecycle data gives administrators the exact dates necessary to map server upgrades and prevent unplanned hosting outages.
Historical Lifecycles and Established Upstream Patterns
A review of earlier version branches reveals a consistent historical rhythm of late-December releases followed by spring end-of-life closures. Observing these past milestones helps forum administrators anticipate future operational cycles:
- Cycle 3.3 launched on 2023-12-25, reached latest version 3.3.13 on 2026-10-23, and carries an end-of-life date of 2027-03-31.
- Cycle 3.2 debuted on 2022-12-25, arrived at latest version 3.2.11 on 2026-03-27, and concluded with an end-of-life date of 2026-03-31.
- Cycle 3.1 arrived on 2021-12-25, published latest version 3.1.7 on 2025-03-26, and reached its end-of-life on 2025-03-26.
- Cycle 3.0 was released on 2020-12-25, delivered latest version 3.0.7 on 2024-04-23, and retired on 2024-04-23.
- Cycle 2.7 opened on 2019-12-25, reached latest version 2.7.8 on 2023-03-30, and concluded on 2023-03-31.
- Cycle 2.6 launched on 2018-12-25, reached latest version 2.6.10 on 2022-04-12, and met its end-of-life on 2022-03-31.
- Cycle 2.5 started on 2017-12-25, delivered latest version 2.5.9 on 2021-04-05, and reached end of life on 2021-03-31.
- Cycle 2.4 debuted on 2016-12-23, published latest version 2.4.10 on 2020-03-31, and closed on 2020-03-31.
This historical pattern underscores the regularity of runtime support schedules, demonstrating how maintenance windows predictably finish at the close of March or late in April.
Practical Planning Steps for Discourse Host Upgrades
To avoid rushed server changes as end-of-life deadlines approach, forum hosts should establish a predictable routine for runtime maintenance. Community managers can take several practical steps to safeguard their forums:
- Verify the active runtime version currently running inside your server environment or Discourse container.
- Review the official release calendars well in advance of the scheduled March retirement deadlines.
- Test forum updates, community themes, and installed plugins in a non-production staging environment prior to running upgrades on your live community.
- Schedule maintenance windows during off-peak community activity to minimize disruption for active members.
By proactively monitoring the runtime timeline from release to retirement, forum administrators can maintain secure, high-performing communities without facing emergency migrations.
Sources
Published October 28, 2026. No affiliate links on this page. Facts come from the sources linked above; check them for updates.