v0.21.1

sleep3r/mtproto.zigv0.21.1May 5, 2026by sleep3r

Upgrading?

AI Summary

v0.21.1 fixes a Docker build failure in v0.21.0 by updating the Dockerfile to use Zig 0.16.0 and republishing signed release artifacts for x86_64, x86_64_v3+aes, and aarch64.

Key Highlights

  • Updated Dockerfile default `ZIG_VERSION` from 0.15.2 to 0.16.0.
  • Rebuilt and re-signed release artifacts for x86_64, x86_64_v3+aes, and aarch64.
  • Published SHA-256 checksums and minisign signatures for all artifacts.

New Features

  • Rebuilt release artifacts with correct Zig version

Full Release Notes

<details open>
<summary>🇷🇺 Что нового (RU)</summary>

## Что решает этот релиз

`v0.21.1` — небольшой patch-релиз поверх большого `v0.21.0`.

Бинарные artifacts `v0.21.0` были собраны и подписаны корректно, но tag-triggered Docker Publish workflow упал: Dockerfile всё ещё скачивал Zig `0.15.2` по умолчанию, а кодовая база уже мигрирована на Zig `0.16.0`. Из-за этого GHCR images для `v0.21.0` не собрались, хотя обычные tar.gz release assets были валидны.

В `v0.21.1` Dockerfile обновлён на Zig `0.16.0`, release artifacts пересобраны и подписаны заново.

> [!NOTE]
> Изменений в `config.toml` не требуется.

> [!TIP]
> Если вы ставите через `mtbuddy install/update` или `deploy/bootstrap.sh`, используйте `latest` или `v0.21.1`. Если вы используете Docker/GHCR, пропускайте `v0.21.0` и берите `v0.21.1`.

## Что изменено

### Docker: сборка образов на Zig 0.16.0 ([#232](https://github.com/sleep3r/mtproto.zig/pull/232))

- Dockerfile default `ZIG_VERSION` обновлён с `0.15.2` до `0.16.0`.
- Пример ручной Docker-сборки в комментарии Dockerfile тоже обновлён на Zig `0.16.0`.
- Release artifacts `mtproto-proxy` и `mtbuddy` для `x86_64`, `x86_64_v3+aes` и `aarch64` пересобраны как `v0.21.1`.
- Для каждого artifact опубликованы SHA-256 checksum и minisign signature.

</details>

---

<details>
<summary>🇬🇧 Release notes (EN)</summary>

## What this release addresses

`v0.21.1` is a small patch release on top of the larger `v0.21.0`.

The `v0.21.0` binary release artifacts were built and signed correctly, but the tag-triggered Docker Publish workflow failed: Dockerfile still downloaded Zig `0.15.2` by default while the codebase had already moved to Zig `0.16.0`. As a result, GHCR images for `v0.21.0` did not publish, even though the regular tar.gz release assets were valid.

`v0.21.1` updates Dockerfile to Zig `0.16.0` and republishes the signed release artifacts.

> [!NOTE]
> No `config.toml` changes are required.

> [!TIP]
> If you install through `mtbuddy install/update` or `deploy/bootstrap.sh`, use `latest` or `v0.21.1`. If you use Docker/GHCR, skip `v0.21.0` and use `v0.21.1`.

## What changed

### Docker: build images with Zig 0.16.0 ([#232](https://github.com/sleep3r/mtproto.zig/pull/232))

- Dockerfile default `ZIG_VERSION` has been updated from `0.15.2` to `0.16.0`.
- The manual Docker build example in the Dockerfile comment now references Zig `0.16.0`.
- `mtproto-proxy` and `mtbuddy` release artifacts for `x86_64`, `x86_64_v3+aes`, and `aarch64` have been rebuilt as `v0.21.1`.
- Every artifact ships with a SHA-256 checksum and minisign signature.

</details>

## Changelog

* chore(main): release 0.21.1 ([#232](https://github.com/sleep3r/mtproto.zig/pull/232)) ([a49eb83](https://github.com/sleep3r/mtproto.zig/commit/a49eb83f9a5ce91e1eb14773f3850a099cd48f1d))

Related Repositories