Codex CLI self-update still fails in 0.139.0: missing SHA-256 digest for Linux x64 musl package

Same issue again with the 0.139.0 update.

This is at least the third time I am reporting the same Codex CLI self-update failure. The built-in updater still offers an update, still invokes the official installer path, and still fails while resolving the SHA-256 digest for the Linux x64 musl package.

Current failure

Codex shows:

✨ Update available! 0.137.0 -> 0.139.0

Release notes: https://github.com/openai/codex/releases/latest

› 1. Update now (runs `sh -c 'curl -fsSL https://chatgpt.com/codex/install.sh | CODEX_NON_INTERACTIVE=1 sh'`)
  2. Skip
  3. Skip until next version

  Press enter to continue

After selecting update:

Updating Codex via `sh -c 'curl -fsSL https://chatgpt.com/codex/install.sh | CODEX_NON_INTERACTIVE=1 sh'`...
==> Updating Codex CLI from 0.137.0 to 0.139.0
==> Detected platform: Linux (x64)
==> Resolved version: 0.139.0
==> Downloading Codex CLI
Could not find SHA-256 digest for codex-package-x86_64-unknown-linux-musl.tar.gz in codex-package_SHA256SUMS.
Error: `sh -c 'curl -fsSL https://chatgpt.com/codex/install.sh | CODEX_NON_INTERACTIVE=1 sh'` failed with status exit status: 1

Platform

Ubuntu 22.04.5 LTS
Linux x64

Why this needs attention

This is no longer a one-off release problem.

The same Codex CLI self-update path has now failed across multiple consecutive update attempts:

0.137.0 -> 0.138.0
0.137.0 -> 0.139.0

The failure is still the same:

Could not find SHA-256 digest for codex-package-x86_64-unknown-linux-musl.tar.gz in codex-package_SHA256SUMS.

That means the official self-update flow is still offering users an update path that cannot complete on this Linux x64 environment.

This is a serious reliability issue for a built-in updater. It repeatedly offers an official update path that fails before installation, across multiple consecutive releases.

At this point, this also raises a process concern: either the installer/update path is not covered by CI/CD on common Ubuntu/Debian-style Linux environments, or the failure is known but has not been prioritized. In either case, the result is the same for users: the official Codex CLI updater remains broken.

Expected behavior

Codex CLI should either:

1. update successfully using the official self-update flow, or
2. not offer a broken update path, or
3. fail with a clear actionable error that explains what dependency or installer condition is missing.

Request

Please treat this as an unresolved installer regression in the official Codex CLI self-update flow.

The checksum lookup for:

codex-package-x86_64-unknown-linux-musl.tar.gz

needs to work reliably on stock Ubuntu/Debian-style Linux systems, including environments where the default awk implementation may not support non-portable regex behavior.

This should not require every user to debug the installer or manually work around the updater.