Skip to content

Releases

wamux-http 0.1.3

Choose a tag to compare

@github-actions github-actions released this 10 Nov 19:54
v0.1.3
e91648d

Added

  • POST /api/sendPollVote votes in a channel poll (#2). The poll is found by
    its message id in the channel's last 300 messages, or named directly by
    WAHA's pollServerId. Each option is sent as the hash of its name exactly
    as the poll spells it, so a name retyped without its emoji variation
    selector or ZWJ answers 400. Every vote carries the whole selection, and an
    empty votes removes the vote.
  • A reply (reply_to on sendText, the media sends and sendContactVcard)
    carries the quoted message's content when the edge stored it, so a
    receiver that does not hold the original still shows what was quoted, as
    GOWS does. Needs wamux v0.2.4.

Changed

  • The wamux contract is v0.2.4, and the reference compose.yaml runs the
    core v0.2.4, whose image ships its own /tmp.

Fixed

  • Starting a session again after a logout, from the API or from the phone,
    left it FAILED instead of asking for a QR: the core keeps a logged-out
    account's identity, logs it in, and WhatsApp answers 401. The edge now
    replaces such an account in the core with a new one under the same name.
  • A stop or a start could be overwritten by an event of the session's
    previous start handled at the same moment: a deleted session could end
    with FAILED after STOPPED (its own logout's LOGGED_OUT), and a
    session started right after a logout could be stopped again. What the
    session's follower writes, and the session.status it publishes, now
    apply only while the session is still in the start it serves.
  • A session whose QR codes ran out stayed SCAN_QR_CODE and retried, and
    between retries (up to a minute) it served the last QR, which the phone
    no longer takes ("couldn't link device"). It now ends FAILED, as GOWS
    ends its QR timeout, until it is started again. A route's 422 for a
    FAILED session now says FAILED, not STOPPED.
  • Starting a session could publish STARTING twice, when its follower read
    the session between the start and its status.
  • The message.ack of my own edit, revoke, reaction or poll vote named the
    peer's LID chat when its event had named the phone chat, because the
    receipt names the peer by LID (#3). Each ack now names the id its event
    went out under.
  • GET /api/contacts by phone number answered pushname: null for a peer
    whose push name the edge had under its LID only (#4), as a history sync
    or a message by LID leaves it. A lookup now fills a missing name from the
    peer's other id, resolved by the core, and a message's push name is kept
    under both of the sender's ids, as whatsmeow keeps it.
  • Logging out or deleting a session left the device in the phone's linked
    devices: the edge stopped the session before asking the core to log out,
    and the core logs out only a connected account. The logout now comes
    first, and a stopped session is connected for it.
  • A reply in a DM to a message stored under the peer's LID chat went out
    as a reply from another chat (the LID as remoteJid). Only a group
    message or a status is quoted from another chat now.
  • An event from the core over 4 MiB (a history sync, 4.67 MB measured)
    broke the session's event stream, losing it. The edge now takes up to
    256 MiB.

Run

Both images run the binary in the tarball below, as uid 10001, from scratch:

  • ghcr.io/llawli/wamux-http:v0.1.3: the binary alone
  • ghcr.io/llawli/wamux-http:v0.1.3-ffmpeg: plus ffmpeg and ffprobe, for voice and video conversion, waveforms and durations

Next to the core: the reference compose.yaml.

Licenses

MIT OR Apache-2.0. The tarball and both images carry THIRD-PARTY-LICENSES.md for the code the binary links. The ffmpeg and ffprobe of the -ffmpeg image are GPL-3.0-or-later: the image carries their licenses in /usr/local/share/doc/ffmpeg, whose SOURCE.md names the release that holds their complete corresponding source.

Verify

The tarball and both images carry a build provenance attestation; the images are published by a job that starts after this release, so they can appear a few minutes later.

gh attestation verify wamux-http-0.1.3-linux-amd64.tar.gz -R LLawli/wamux-http
gh attestation verify oci://ghcr.io/llawli/wamux-http:v0.1.3 -R LLawli/wamux-http

wamux-http 0.1.2

Choose a tag to compare

@github-actions github-actions released this 26 Oct 20:15
v0.1.2
0aac351

Added

  • A reply_to naming a message in another chat sends a private reply (to a
    group message) or a reply to a status, quoting the message in its own
    chat: the stored message's, or the chat in a full WAHA message id.
  • me.reachoutTimelock and the WORKING status's data report WhatsApp's
    reachout restriction as the core notifies it; a change while WORKING is a
    new WORKING event.
  • scripts/sync-contracts.sh refreshes the pinned wamux or WAHA contract.

Changed

  • The wamux contract is v0.2.2, and the reference compose.yaml runs the
    core v0.2.2 (a static musl binary on scratch).
  • A poll to a channel with several answers is sent as WA Web publishes it
    (selectable count 0), which wamux v0.2.2 requires.
  • POST /api/sendPollVote to a channel answers 501. It never voted there:
    a channel poll is voted by its server id with hashed options, which this
    edge does not keep, and since wamux v0.2.2 it has no secret, so the
    answer had become a misleading 422 "Poll not found".

Fixed

  • Logging out a started session could leave it FAILED instead of back at
    SCAN_QR_CODE, when it started again in the same millisecond as the
    core's logout: the old LOGGED_OUT was applied to the new start.

Run

Both images run the binary in the tarball below, as uid 10001, from scratch:

  • ghcr.io/llawli/wamux-http:v0.1.2: the binary alone
  • ghcr.io/llawli/wamux-http:v0.1.2-ffmpeg: plus ffmpeg and ffprobe, for voice and video conversion, waveforms and durations

Next to the core: the reference compose.yaml.

Licenses

MIT OR Apache-2.0. The tarball and both images carry THIRD-PARTY-LICENSES.md for the code the binary links. The ffmpeg and ffprobe of the -ffmpeg image are GPL-3.0-or-later: the image carries their licenses in /usr/local/share/doc/ffmpeg, whose SOURCE.md names the release that holds their complete corresponding source.

Verify

The tarball and both images carry a build provenance attestation; the images are published by a job that starts after this release, so they can appear a few minutes later.

gh attestation verify wamux-http-0.1.2-linux-amd64.tar.gz -R LLawli/wamux-http
gh attestation verify oci://ghcr.io/llawli/wamux-http:v0.1.2 -R LLawli/wamux-http

wamux-http 0.1.1

Choose a tag to compare

@github-actions github-actions released this 22 Oct 15:31
v0.1.1
449160e

Fixed

  • License notices. The tarball and both images ship
    THIRD-PARTY-LICENSES.md: the texts of every Go module the binary links,
    with where its source is. The -ffmpeg image ships, in
    /usr/local/share/doc/ffmpeg, the GPL-3.0 text and the license of each of
    the components ffmpeg links, and points at their complete corresponding
    source, now published as the static-ffmpeg-9.0.2-source release
    (v0.1.0's images lacked all of this).

Run

Both images run the binary in the tarball below, as uid 10001, from scratch:

  • ghcr.io/llawli/wamux-http:v0.1.1: the binary alone
  • ghcr.io/llawli/wamux-http:v0.1.1-ffmpeg: plus ffmpeg and ffprobe, for voice and video conversion, waveforms and durations

Next to the core: the reference compose.yaml.

Licenses

MIT OR Apache-2.0. The tarball and both images carry THIRD-PARTY-LICENSES.md for the code the binary links. The ffmpeg and ffprobe of the -ffmpeg image are GPL-3.0-or-later: the image carries their licenses in /usr/local/share/doc/ffmpeg, whose SOURCE.md names the release that holds their complete corresponding source.

Verify

The tarball and both images carry a build provenance attestation; the images are published by a job that starts after this release, so they can appear a few minutes later.

gh attestation verify wamux-http-0.1.1-linux-amd64.tar.gz -R LLawli/wamux-http
gh attestation verify oci://ghcr.io/llawli/wamux-http:v0.1.1 -R LLawli/wamux-http

wamux-http 0.1.0

Choose a tag to compare

@github-actions github-actions released this 22 Oct 13:46
v0.1.0
dc3ba3b

Added

  • WAHA-compatible HTTP server on top of the wamux core (contract pinned to
    wamux v0.2.1 and WAHA 2026.8.2).
  • Sessions: create, list, get, update, delete, start, stop, restart, logout,
    me, and the deprecated body-named forms. A session is a wamux account;
    its desired state survives restarts and it reconnects after a drop, except
    after a logout or a ban.
  • Pairing by QR (PNG, base64 JSON or raw value) and by phone code.
  • API keys in the WAHA Plus model: the admin key from WAHA_API_KEY
    (plain or sha512:), and session keys with actions. Keys are stored as
    hashes, so listings show them masked.
  • A session key can cover several sessions: /api/keys takes and returns
    sessions next to WAHA's session.
  • Container images on GHCR, both FROM scratch with one static binary and
    run as uid 10001: ghcr.io/llawli/wamux-http:vX.Y.Z (35 MB) and
    vX.Y.Z-ffmpeg (430 MB, with ffmpeg and ffprobe for voice and video
    conversion). A static Linux x86_64 tarball with every release; the tarball
    and both images carry the same binary, with provenance attestations.
  • Reference compose.yaml running the core and this edge from GHCR (it
    replaces deploy/docker-compose.yml).
  • wamux-http --version.
  • CA roots compiled in, used when the host has none (a scratch container):
    https webhooks and media fetches verify there too.
  • WebP images get thumbnails without ffmpeg.
  • Web panel at /dashboard, unlocked with the admin key: pair sessions by QR
    or phone code with live status, start, stop, restart, log out and delete
    them, edit their webhooks and metadata and the account's name, about and
    picture, and create, deactivate and revoke API keys.
    WAHA_DASHBOARD_ENABLED=false turns it off.
  • Webhooks with WAHA's envelope, headers, HMAC-SHA512 signature and retry
    policies, delivered from a durable outbox.
  • Every WAHA operation not implemented yet answers WAHA's 501;
    docs/coverage.md lists them.
  • Built to run several instances on one store: sessions are owned by lease.
  • /ws: every event, in the webhook envelope, filtered by session and event.
  • Incoming messages, acks, reactions, edits, revokes, poll votes, presence,
    group, call, label and archive events as WAHA webhooks, honoring
    config.ignore; history sync fills chats, messages and contacts without
    webhooks.
  • Chats (list, overview, messages, picture, read, archive, unread, delete,
    edit), label reads, presence, and the deprecated GET /api/messages.
  • Sends: text with link previews, image, file, voice, video, sticker,
    contact, poll and poll vote, buttons reply, reactions, stars, read
    receipts and typing. Sends answer a WAMessage carrying _data.
  • Text, image and video statuses, and status delete.
  • Voice and video conversion with ffmpeg, and /api/files serving received
    media, downloaded from the core on first request.
  • Client URLs are fetched behind an SSRF guard
    (WAMUX_HTTP_MEDIA_ALLOW_PRIVATE, WAMUX_HTTP_MEDIA_MAX_BYTES,
    WAMUX_HTTP_MEDIA_FETCH_TIMEOUT).
  • Contacts and LIDs, block and unblock, groups (create, list, participants,
    admins, invites, join requests, security settings, picture), profile
    (name, about, picture), channels (list, info, message preview, create,
    follow, unfollow, mute, unmute) and call rejection. Block, about, the group
    approval and add modes, the channel writes and call rejection need wamux
    v0.2.1; on v0.2.0 they answer 501.

Run

Both images run the binary in the tarball below, as uid 10001, from scratch:

  • ghcr.io/llawli/wamux-http:v0.1.0: the binary alone
  • ghcr.io/llawli/wamux-http:v0.1.0-ffmpeg: plus ffmpeg and ffprobe, for voice and video conversion, waveforms and durations

Next to the core: the reference compose.yaml.

Verify

The tarball and both images carry a build provenance attestation; the images are published by a job that starts after this release, so they can appear a few minutes later.

gh attestation verify wamux-http-0.1.0-linux-amd64.tar.gz -R LLawli/wamux-http
gh attestation verify oci://ghcr.io/llawli/wamux-http:v0.1.0 -R LLawli/wamux-http

Licenses (added after release)

This release's images shipped without the license notices that v0.1.1 adds; use v0.1.1. The ffmpeg and ffprobe in ghcr.io/llawli/wamux-http:v0.1.0-ffmpeg are the same binaries as in v0.1.1 (mwader/static-ffmpeg:9.0.2), GPL-3.0-or-later. Their complete corresponding source is the static-ffmpeg-9.0.2-source release, and the GPL text and every component's license are in /usr/local/share/doc/ffmpeg of the v0.1.1-ffmpeg image and in packaging/ffmpeg/doc. The notices of what the wamux-http binary links are in THIRD-PARTY-LICENSES.md.

Source of the static ffmpeg (static-ffmpeg-9.0.2-source)

Choose a tag to compare

@LLawli LLawli released this 22 Oct 15:27
static-ffmpeg-9.0.2-source
8b9810e

Corresponding source of the ffmpeg and ffprobe binaries in the
ghcr.io/llawli/wamux-http:*-ffmpeg images: ffmpeg 9.0.2 as built by
wader/static-ffmpeg (image
mwader/static-ffmpeg:9.0.2), GPL-3.0-or-later.

Asset Holds
static-ffmpeg-9.0.2-source-build.tar the build scripts (wader/static-ffmpeg at the commit the image was built from)
static-ffmpeg-9.0.2-source-upstream.tar every source tarball the build downloads, as pinned by sha256
static-ffmpeg-9.0.2-source-git.tar every repository it clones, at the pinned commit, with submodules
static-ffmpeg-9.0.2-source-extra.tar what component builds fetch themselves: libjxl's third_party, cargo crates, meson wraps
static-ffmpeg-9.0.2-source-alpine.tar the Alpine 3.20 packages linked statically: APKBUILDs, patches and source files
static-ffmpeg-9.0.2-source-MANIFEST.json every file, its origin and sha256

The bundle is complete: the build was run again from it with no network
(packaging/ffmpeg in this repository has the scripts that collect it, rebuild
from it and extract the license texts the image ships).