Go's support policy is short and simple; here is what it means in practice.
1 min read
Each major Go release is supported until there are two newer major releases, according to the official Go release policy. Because Go ships a new major version about every six months, that works out to roughly one year of support (an estimate based on the cadence, not a fixed date).
Supported releases get minor point releases for critical problems, including security fixes. Once two newer majors exist, the old one gets no more fixes.
Go has historically released new majors around February and August each year. Treat future dates as estimates until the Go team announces them.
Stay within the two newest Go versions. The go directive and toolchain line in go.mod make it easy to test and move to a newer toolchain.
Related: /blog/when-does-node-js-24-reach-end-of-life
Related: /blog/when-does-python-3-11-reach-end-of-life
Related: /blog/when-does-postgresql-14-reach-end-of-life
Lab evidence
Facts in this draft were checked on 12 Oct 2026 against the primary sources listed in the body (official docs, release schedules or Google/YouTube help pages). No benchmarks or timings were run, so the post makes no performance or measurement claims; dates are quoted as published by the maintainers, and any estimate is labelled as such.
Explore the product
Freelancers and devs who want to turn coding skills into paid site builds
Released October 2024, now security-only, ending 2029. What that means for your projects.
Summary14 Oct 20263 min read
Both cut a string at a separator, but they fail in different ways. We ran them on Python 3.13.5 to show where partition() is safer and where split() is the right tool.
Summary2 Nov 20263 min read
What changes when you swap sort() for toSorted(), with a real 1-million-item Node.js benchmark and the support table.
Summary1 Nov 20263 min read