# digest_mismatch

> The uncompressed tar does not hash to the expected release digest.

The uncompressed tar does not hash to the expected release digest.

| | |
| --- | --- |
| Kind | Build or validation problem |
| Reported by | Archive validation (registry, room hosts, disko publish) |
| `disko` exit code | 1 (problems) |

The archive's uncompressed tar does not hash to the release digest that was
expected for it. The digest (`blake3:` plus 64 hex characters) identifies a
release, so an archive with a different digest is a different release.

## Why it happens

A room host reports this code when a downloaded archive does not match the
digest the registry recorded for the release. It points to a corrupted or
altered download or cache, not to a mistake in your project. Creators do not
normally see it.

## Wrong

```text
expected  blake3:9f2c…e41a
archive   blake3:07b1…c3d0
```

## Right

```text
expected  blake3:9f2c…e41a
archive   blake3:9f2c…e41a
```

Download the release again. If it keeps failing, check what sits between the
host and the registry (caches, proxies, disk).

## See also

- [Releases](/registry/releases)