GleamEnd of Life (EOL) Dates & Support Status

Active

Programming LanguagesLatest Version: 1.18.1Latest Release: Aug 1, 2026

Gleam is a statically typed functional programming language for building type-safe systems on the Erlang VM.

Support summary

Gleam 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

0 lts

Versions

Latest Version

1.18.1

Active Support

EOL

Lifecycle Timeline

Mar 4, 2024As of Sep 27, 2026

1Active · Date not announced

ActiveSecurityEOLHistorical phase unknown

Bars show history up to the snapshot date. Gray intervals lack dated support boundaries; arrows indicate an unannounced EOL date, not a support guarantee.

Versions

Release	Release Date	Active Support	EOL	Latest Version	LTS	Status
1	Mar 4, 2024	Maintained	Date not announced	1.18.1	No	Active

Data sources

Sources

endoflife.date

Embed this badge

Show Gleam's live support status in your README, docs, or dashboard. The badge is a static SVG served from eol.wiki and follows the lifecycle data above.

Markdown

[![Gleam end-of-life status](https://eol.wiki/badge/gleam.svg)](https://eol.wiki/gleam/)

HTML

<a href="https://eol.wiki/gleam/"><img src="https://eol.wiki/badge/gleam.svg" alt="Gleam end-of-life status" height="20"></a>

All badges & lifecycle API →

Frequently Asked Questions

Is it safe to continue using Gleam 1?

Gleam 1 is currently supported and receiving updates. You can continue using it safely until its end-of-life date.

What is the latest version of Gleam?

The latest version of Gleam is 1.18.1, released in the 1 release cycle.

How many versions of Gleam are currently supported?

Gleam currently has 1 actively supported version(s): 1.

When does Gleam 1 reach end of life?

Gleam 1 does not have a specific end-of-life date announced yet.

What should I do when Gleam reaches end of life?

When a Gleam 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.