ShutdownRadar
Support lifecycle

gleam end of life dates — full support timeline

18 of 19 tracked gleam releases have already reached end of life. The dates below are published support dates, not estimates.

Version support timeline

ReleaseReleasedEnd of lifeLatestStatus
1.182026-07-29not announced1.18.0supported
1.172026-06-022026-07-291.17.0ended
1.162026-04-242026-06-021.16.0ended
1.152026-03-162026-04-241.15.4ended
1.142025-12-252026-03-161.14.0ended
1.132025-10-192025-12-251.13.0ended
1.122025-08-052025-10-191.12.0ended
1.112025-06-022025-08-051.11.1ended
1.102025-04-142025-06-021.10.0ended
1.92025-03-082025-04-141.9.1ended
1.82025-02-072025-03-081.8.1ended
1.72025-01-042025-02-071.7.0ended
1.62024-11-182025-01-041.6.3ended
1.52024-09-192024-11-181.5.1ended
1.42024-08-022024-09-191.4.1ended
1.32024-07-092024-08-021.3.2ended
1.22024-05-272024-07-091.2.1ended
1.12024-04-162024-05-271.1.1ended
1.02024-03-042024-04-161.0.0ended

Who is affected

Anyone running an unsupported gleam release. After end of life a version stops receiving security patches, which typically becomes an audit or compliance finding before it becomes an outage. Upgrading to a supported release is the migration path; the table above shows which releases still qualify.

Source

These dates are maintained by endoflife.date/gleam, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.

Get told before the next gleam deadline

You are reading this because a gleam release is losing support. The next one will arrive the same way — quietly, months before an auditor finds it. A free weekly email lists every gleam and related deadline as it is announced, with exact dates and primary sources.

Watch gleam deadlines Team monitoring pilot →

Takes about twenty seconds. No account, no card, no tracking.

All upcoming deadlines · Full archive