← ← Back to all products
Sourcegraph
Active
DevOps & CI/CDLatest Version: 7.4.0Latest Release: Jun 11, 2026
Sourcegraph is a code intelligence platform for searching, navigating, and understanding code at scale.
Support summary
Sourcegraph currently has supported cycles. Track the next EOL date and validate upgrades before your change window.
What do EOL and support statuses mean?Next EOL
No announced EOL date is currently listed.
Supported cycles
2
0 lts
Versions
4
Latest Version
7.4.0
Active Support
2
EOL
2
Lifecycle Timeline
Today ↓
7
7
6
6
5
5
4
4
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 7 | Feb 25, 2026 | Yes | No | 7.4.0 | No | Active |
| 6 | Jan 29, 2025 | Yes | No | 6.12.5040 | No | Active |
| 5 | Mar 22, 2023 | No | Jan 29, 2025 | 5.11.6271 | No | EOL |
| 4 | Sep 22, 2022 | No | May 22, 2023 | 4.5.1 | No | EOL |
Data sources
Sources
Frequently Asked Questions
Which versions of Sourcegraph have reached end of life?
The following Sourcegraph versions have reached end of life and no longer receive security updates: 5, 4. It is recommended to upgrade to a supported version.
Is it safe to continue using Sourcegraph 5?
Sourcegraph 5 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 Sourcegraph?
The latest version of Sourcegraph is 7.4.0, released in the 7 release cycle.
How many versions of Sourcegraph are currently supported?
Sourcegraph currently has 2 actively supported version(s): 7, 6.
When does Sourcegraph 7 reach end of life?
Sourcegraph 7 does not have a specific end-of-life date announced yet.
What should I do when Sourcegraph reaches end of life?
When a Sourcegraph 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.