EOL.Wiki EOL.Wiki
← ← Back to all products

Discourse

Active
Other Latest Version: 2026.5.0 Latest Release: May 28, 2026

Versions

9

Latest Version

2026.5.0

Active Support

3

EOL

6

Lifecycle Timeline

Today
2026.5
2026.5
2026.4
2026.4
2026.3
2026.3
2026.2
2026.2
2026.1
2026.1
2025.12
2025.12
2025.11
2025.11
3.5
3.5
3.4
3.4
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
2026.5May 28, 2026YesJul 31, 20262026.5.0No
Active
2026.4Apr 28, 2026YesJun 30, 20262026.4.1No
Active
2026.3Mar 31, 2026NoMay 28, 20262026.3.1No
EOL
2026.2Feb 26, 2026NoApr 28, 20262026.2.2No
EOL
2026.1Jan 28, 2026YesSep 30, 20262026.1.4
Yes
Active
2025.12Dec 30, 2025NoFeb 26, 20262025.12.2No
EOL
2025.11Nov 25, 2025NoJan 28, 20262025.11.2No
EOL
3.5Aug 19, 2025NoJan 28, 20263.5.4
Yes
EOL
3.4Feb 4, 2025NoAug 19, 20253.4.7
Yes
EOL

Frequently Asked Questions

Which versions of Discourse have reached end of life?
The following Discourse versions have reached end of life and no longer receive security updates: 2026.3, 2026.2, 2025.12, 2025.11, 3.5, 3.4. It is recommended to upgrade to a supported version.
Is it safe to continue using Discourse 2026.3?
Discourse 2026.3 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Discourse?
The latest version of Discourse is 2026.5.0, released in the 2026.5 release cycle.
How many versions of Discourse are currently supported?
Discourse currently has 3 actively supported version(s): 2026.5, 2026.4, 2026.1.
When does Discourse 2026.5 reach end of life?
Discourse 2026.5 is scheduled to reach end of life on Jul 31, 2026.
What should I do when Discourse reaches end of life?
When a Discourse version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.