# Erlang OTP 28.0 Released

**URL:** <https://erlangforums.com/t/erlang-otp-28-0-released/4772>\
**Category:** Erlang News\
**Tags:** erlang-release\
**Created:** [May 21, 2025, 10:03am UTC](https://erlangforums.com/t/erlang-otp-28-0-released/4772 "2025-05-21T10:03:24Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![proxyles](https://erlangforums.com/letter_avatar_proxy/v4/letter/p/9de053/32.png) [@proxyles](https://erlangforums.com/u/proxyles)\
**Post date:** [May 21, 2025, 10:03am UTC](https://erlangforums.com/t/erlang-otp-28-0-released/4772/1 "2025-05-21T10:03:24Z")

</div>

## OTP 28.0

Erlang/OTP 28 is a new major release with new features, improvements as well as a few incompatibilities. Some of the new features are highlighted below.

Many thanks to all contributors!

Starting with this release, a source [Software Bill of Materials (SBOM)](https://www.cisa.gov/sites/default/files/2023-04/sbom-types-document-508c.pdf) will describe the release on the [Github Releases](https://github.com/erlang/otp/releases) page.  
We welcome feedback on the SBOM.

## New language features

- Functionality making it possible for processes to enable reception of [priority messages](https://erlang.org/doc/system/ref_man_processes.html#priority-messages) has been introduced in accordance with [EEP 76](https://www.erlang.org/eeps/eep-0076).

- Comprehensions have been extended with “zip generators” allowing multiple generators to be run in parallel. For example, `[A+B || A <- [1,2,3] && B <- [4,5,6]]` will produce `[5,7,9]`.

- Generators in comprehensions can now be strict, meaning that if the generator pattern does not match, an exception will be raised instead of silently ignore the value that didn’t match.

- It is now possible to use any base for floating point numbers as per [EEP 75: Based Floating Point Literals](https://www.erlang.org/eeps/eep-0075).

## Compiler and JIT improvements

- For certain types of errors, the compiler can now suggest corrections. For example, when attempting to use variable `A` that is not defined but `A0` is, the compiler could emit the following message: `variable 'A' is unbound, did you mean 'A0'?`

- The size of an atom in the Erlang source code was limited to 255 bytes in previous releases, meaning that an atom containing only emojis could contain only 63 emojis. While atoms are still only allowed to contain 255 characters, the number of bytes is no longer limited.

- The `warn_deprecated_catch` option enables warnings for use of old-style catch expressions on the form `catch Expr` instead of the modern `try` … `catch` … `end`.

- Provided that the map argument for a `maps:put/3` call is known to the compiler to be a map, the compiler will replace such calls with the corresponding update using the map syntax.

- Some BIFs with side-effects (such as `binary_to_atom/1`) are optimized in `try` … `catch` in the same way as guard BIFs in order to gain performance.

- The compiler’s alias analysis pass is now both faster and less conservative, allowing optimizations of records and binary construction to be applied in more cases.

## ERTS

- The `trace:system/3` function has been added. It has a similar interface as `erlang:system_monitor/2` but it also supports trace sessions.

- `os:set_signal/2` now supports setting handlers for the `SIGWINCH`, `SIGCONT`, and `SIGINFO` signals.

- The two new BIFs `erlang:processes_iterator/0` and `erlang:process_next/1` make it possible to iterate over the process table in a way that scales better than `erlang:processes/0`.

## Shell and terminal

- The erl -noshell mode has been updated to have two sub modes called `raw` and `cooked`, where `cooked` is the old default behaviour and `raw` can be used to bypass the line-editing support of the native terminal. Using `raw` mode it is possible to read keystrokes as they occur without the user having to press Enter. Also, the `raw` mode does not echo the typed characters to stdout.

- The shell now prints a help message explaining how to interrupt a running command when stuck executing a command for longer than 5  
seconds.

## STDLIB

- The `join(Binaries, Separator)` function that joins a list of binaries has been added to the [`binary`](https://erlang.org/documentation/doc-16.0/lib/stdlib-7.0/doc/html/binary.html) module.

- By default, sets created by module [`sets`](https://erlang.org/documentation/doc-16.0/lib/stdlib-7.0/doc/html/sets.html) will now be represented as maps.

- Module [`re`](https://erlang.org/documentation/doc-16.0/lib/stdlib-7.0/doc/html/re.html) has been updated to use the newer PCRE2 library instead of the PCRE library.

- There is a new `zstd` module that does [Zstandard](https://facebook.github.io/zstd/) compression.

## Public\_key

- The ancient ASN.1 modules used in `public_key` has been replaced with more modern versions, but we have strived to keep the documented Erlang API for the `public_key` application compatible.

## Dialyzer

- [EEP 69: Nominal Types](https://www.erlang.org/eeps/eep-0069) has been implemented.

## SSL

- The data handling for tls-v1.3 has been optimized.

## Emacs mode (in the Tools application)

- The `indent-region` in Emacs command will now handle multiline strings better.

For more details about new features and potential incompatibilities see the [README](https://erlang.org/download/otp_src_28.0.readme).

---

<div class="post-metadata">

**Author:** ![zabrane](https://erlangforums.com/letter_avatar_proxy/v4/letter/z/7ba0ec/32.png) [@zabrane](https://erlangforums.com/u/zabrane)\
**Post date:** [May 21, 2025, 12:29pm UTC](https://erlangforums.com/t/erlang-otp-28-0-released/4772/2 "2025-05-21T12:29:33Z")

</div>

Congrats for the `28.0` release 🚀

It successffuly compiled on:

```bash
## macOS Silicon (DEV env)
$ sw_vers
ProductName: macOS
ProductVersion: 15.4.1
$ uname -m
arm64

## Ubuntu Linux (PROD env)
$ uname -a
Linux xxxxx 5.15.0-139-generic 149-Ubuntu SMP Fri Apr 11 22:06:13 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux

```

We gonna start testing it next week and report any issue here.

---

<div class="post-metadata">

**Author:** ![garazdawi](https://erlangforums.com/user_avatar/erlangforums.com/garazdawi/32/175_2.png) [@garazdawi](https://erlangforums.com/u/garazdawi)\
**Post date:** [May 21, 2025, 1:55pm UTC](https://erlangforums.com/t/erlang-otp-28-0-released/4772/3 "2025-05-21T13:55:22Z")

</div>

You should also check out the [release highlight post](https://www.erlang.org/blog/highlights-otp-28/)!

---

<div class="post-metadata">

**Author:** ![zabrane](https://erlangforums.com/letter_avatar_proxy/v4/letter/z/7ba0ec/32.png) [@zabrane](https://erlangforums.com/u/zabrane)\
**Post date:** [May 21, 2025, 10:17pm UTC](https://erlangforums.com/t/erlang-otp-28-0-released/4772/5 "2025-05-21T22:17:55Z")

</div>

@garazdawi Does the following calls the new `hibernate/0` highlighted in the post?

```erlang
...
handle_continue(final_state, State) ->
    {noreply, State, hibernate}.

```

---

<div class="post-metadata">

**Author:** ![garazdawi](https://erlangforums.com/user_avatar/erlangforums.com/garazdawi/32/175_2.png) [@garazdawi](https://erlangforums.com/u/garazdawi)\
**Post date:** [May 22, 2025, 6:47am UTC](https://erlangforums.com/t/erlang-otp-28-0-released/4772/6 "2025-05-22T06:47:18Z")

</div>

Yes I think it should, it was introduced by @Maria-12648430 in [Augment `gen_server` timeout handling by Maria-12648430 · Pull Request #9287 · erlang/otp · GitHub](https://github.com/erlang/otp/pull/9287).

---

<div class="post-metadata">

**Author:** ![zabrane](https://erlangforums.com/letter_avatar_proxy/v4/letter/z/7ba0ec/32.png) [@zabrane](https://erlangforums.com/u/zabrane)\
**Post date:** [May 22, 2025, 8:54am UTC](https://erlangforums.com/t/erlang-otp-28-0-released/4772/7 "2025-05-22T08:54:17Z")

</div>

> [@garazdawi](#):
>
> Yes I think it should, it was introduced by @Maria-12648430 in [Augment `gen_server` timeout handling by Maria-12648430 · Pull Request #9287 · erlang/otp · GitHub](https://github.com/erlang/otp/pull/9287).

Well done guys @garazdawi @Maria-12648430

---

<div class="post-metadata">

**Author:** ![Maria-12648430](https://erlangforums.com/user_avatar/erlangforums.com/maria-12648430/32/604_2.png) [@Maria-12648430](https://erlangforums.com/u/Maria-12648430)\
**Post date:** [May 22, 2025, 9:52am UTC](https://erlangforums.com/t/erlang-otp-28-0-released/4772/8 "2025-05-22T09:52:47Z")

</div>

Don’t forget @raimo who took the lead on this and related PRs and @juhlig who took it over for a while when I was n/a 🫶 Thanks guys, always great to work with you 🥰

---

<div class="post-metadata">

**Author:** ![zabrane](https://erlangforums.com/letter_avatar_proxy/v4/letter/z/7ba0ec/32.png) [@zabrane](https://erlangforums.com/u/zabrane)\
**Post date:** [May 22, 2025, 10:54am UTC](https://erlangforums.com/t/erlang-otp-28-0-released/4772/9 "2025-05-22T10:54:10Z")

</div>

You’re absolutely right @Maria-12648430. Thanks to all contributors and to the Erlang CORE team.

It was out of the excitement I always have when a new Erlang release is out that I initially missed acknowledging everyone properly.

Special **bravo** to @raimo@juhlig🎉

---

<div class="post-metadata">

**Author:** ![dlachausse](https://erlangforums.com/user_avatar/erlangforums.com/dlachausse/32/2067_2.png) [@dlachausse](https://erlangforums.com/u/dlachausse)\
**Post date:** [May 22, 2025, 12:15pm UTC](https://erlangforums.com/t/erlang-otp-28-0-released/4772/10 "2025-05-22T12:15:20Z")

</div>

If you use the built-in Emacs mode, I made a simple script to automate configuration of your .emacs file for it…

> **[GitHub - dlachausse/erlmacs: Simple script to update your .emacs file for...](https://github.com/dlachausse/erlmacs)**
>
> Simple script to update your .emacs file for Erlang development

---

<div class="post-metadata">

**Author:** ![obi458](https://erlangforums.com/letter_avatar_proxy/v4/letter/o/ee59a6/32.png) [@obi458](https://erlangforums.com/u/obi458)\
**Post date:** [May 23, 2025, 3:30am UTC](https://erlangforums.com/t/erlang-otp-28-0-released/4772/11 "2025-05-23T03:30:39Z")

</div>

Is there a roadmap for TLS 1.3 with PSK and/or SRP?

---

<div class="post-metadata">

**Author:** ![ingela](https://erlangforums.com/letter_avatar_proxy/v4/letter/i/53a042/32.png) [@ingela](https://erlangforums.com/u/ingela)\
**Post date:** [May 23, 2025, 6:57am UTC](https://erlangforums.com/t/erlang-otp-28-0-released/4772/12 "2025-05-23T06:57:59Z")

</div>

TLS-1.3 already supports PSK (just not PSK only) which should be a fairly easy addition once you know what you want the API to look like. As it is part of TLS-1.3 RFC it is on the RoadMap but not top prioritized. If you want to help out a PR is welcome. As for SRP I guess it has it own RFC and is then less prioritize compared to PSK only that is part of the TLS-1.3 RFC.

---

<div class="post-metadata">

**Author:** ![MononcQc](https://erlangforums.com/user_avatar/erlangforums.com/mononcqc/32/417_2.png) [@MononcQc](https://erlangforums.com/u/MononcQc)\
**Post date:** [May 24, 2025, 1:56am UTC](https://erlangforums.com/t/erlang-otp-28-0-released/4772/13 "2025-05-24T01:56:56Z")

</div>

Took some time out of vacation today to publish Rebar3 3.25.0 for Erlang 28.0 compatibility: [Release 3.25.0 · erlang/rebar3 · GitHub](https://github.com/erlang/rebar3/releases/tag/3.25.0)

---

<div class="post-metadata">

**Author:** ![zabrane](https://erlangforums.com/letter_avatar_proxy/v4/letter/z/7ba0ec/32.png) [@zabrane](https://erlangforums.com/u/zabrane)\
**Post date:** [May 24, 2025, 7:31am UTC](https://erlangforums.com/t/erlang-otp-28-0-released/4772/14 "2025-05-24T07:31:09Z")

</div>

@MononcQc switched our DEV env to `rebar 3.25.0`. All good.

---

<div class="post-metadata">

**Author:** ![schnef](https://erlangforums.com/letter_avatar_proxy/v4/letter/s/ad7895/32.png) [@schnef](https://erlangforums.com/u/schnef)\
**Post date:** [May 24, 2025, 7:40am UTC](https://erlangforums.com/t/erlang-otp-28-0-released/4772/15 "2025-05-24T07:40:14Z")

</div>

Thank you!