Last checked and updated on 22 May 2026
Go Lifecycle & End of Life (EOL) Policy
Go follows a straightforward release policy that keeps the language stable while ensuring security. Each major version gets support until two newer major releases come out. This means the two most recent major versions are always actively maintained.
During this support window, the team issues minor revisions as needed. These include fixes for bugs across the compiler, runtime, tools, and standard library packages. More importantly, they cover critical security problems to keep applications safe.
Major releases happen about every six months, with minor patches in between when required. The policy avoids long-term branches or separate LTS tracks, focusing instead on encouraging upgrades to the latest versions for the best experience.
Once a version falls outside the two most recent, it reaches end of life. No further updates, including security ones, are provided for it. This setup promotes keeping projects current with modern Go features and improvements.
Developers benefit from this by planning regular updates, aligning with the predictable cadence to maintain secure and efficient codebases.
| Policy Element | Details |
|---|---|
| Supported Versions | The two most recent major releases. |
| Updates Provided | Minor revisions for bugs and critical security issues. |
| EOL Trigger | When two newer majors are available. |
This approach keeps the ecosystem healthy by balancing stability with timely advancements.
Risks of Using End-of-Life (EOL) Versions
Continuing with Go versions past their support period means missing out on fixes for newly found vulnerabilities, leaving code open to potential exploits in the runtime or standard library.
Newer tools, libraries, or operating systems might not work well with older releases, causing build issues or runtime problems. Performance enhancements and bug resolutions in later versions stay out of reach.
In regulated environments, using unsupported software can complicate compliance efforts or audits. Teams spend more time on custom workarounds instead of leveraging official improvements.
Staying within supported releases avoids these challenges and ensures access to ongoing safeguards.
Key Risks
- Unpatched security flaws.
- Compatibility gaps.
- Compliance concerns.
- Higher maintenance costs.
What Happens After Go Reaches EOL
When a Go version hits EOL, all official updates stop, including patches for security or bugs.
Existing programs still compile and run, but without protection from future issues discovered in the older codebase.
This is the cue to upgrade to one of the supported majors, gaining better tools and safety.
| Post-EOL Outcome | Implications |
|---|---|
| Updates | None available. |
| Recommended Action | Upgrade to supported version. |
People Also Ask -- Go EOL & Support Questions
Q1: How long is each Go major version supported?
Until two newer major releases are available.
Q2: What fixes do supported Go versions receive?
Minor revisions for bugs and critical security problems.
Q3: What risks come with using an EOL Go version?
No patches for new vulnerabilities or bugs.
Q4: What happens when a Go version reaches EOL?
Official updates stop completely.
Q5: How many Go versions are supported at once?
Always the two most recent major ones.
Tracking & Monitoring Go EOL Dates
Check the release policy page for the current rule on supported versions.
Release notes and blog announcements highlight new majors, signaling when older ones approach EOL.
Monitoring Tips
- Review release history.
- Follow blog updates.
- Note major cadence.
How To Check Your Go Version
Run the version command:
go version
It outputs something like go1.24.0 for the installed binary.
In code:
fmt.Println(runtime.Version())