---
summary: "The Docker build stage runs on the build host's platform, so the multi-arch image publishes again — 2.3.1 shipped to npm and the registry but no container image"
breaking: false
security: false
---

# 2.3.2 — 2026-08-22

## Fixed

- **The multi-arch container image publishes again.** The build stage was declared for the *target* platform, so on an arm64 build host the `linux/amd64` half ran under emulation, where Bun 1.4.0 aborts during `bun run build`. The whole multi-arch push failed with it, and **2.3.1 reached npm, the MCP Registry, and GitHub Releases without publishing a container image** — `ghcr.io/cyanheads/ntfy-mcp-server:2.3.1` does not exist. Pull `2.3.2` instead; nothing else differs between the two.

  The build stage now pins to `$BUILDPLATFORM`. It emits JavaScript and only `dist/` crosses into the production stage, which runs its own target-architecture install, so the build never needs emulating. Bun stays on `1.4.0` in both stages.