Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

docs: name 0.26.0 where the text says the next release

Yudhi Armyndharisb0644aba3f00
diff --git a/docs/11-operational-runbooks.md b/docs/11-operational-runbooks.md
index 15719ecf6..05cccac04 100644
--- a/docs/11-operational-runbooks.md
+++ b/docs/11-operational-runbooks.md
@@ -664,7 +664,7 @@ curl -H "X-API-Key: $API_KEY" http://localhost:2785/api/health
```
> Restoring `sessions/` is required, not optional, when the rollback crosses a browser major upgrade (on
-> amd64, 0.23.5 moved Chrome for Testing from 146 to 153 and the release after 0.25.0 moves it to 156; arm64
+> amd64, 0.23.5 moved Chrome for Testing from 146 to 153 and 0.26.0 moves it to 156; arm64
> runs the chromium Debian shipped when each image was built), and the backup must predate the first start
> on the newer image; a daily backup taken after the upgrade does not qualify. An older Chrome silently
> deletes the IndexedDB of a profile a newer Chrome has opened, which is where whatsapp-web.js keeps the
diff --git a/docs/12-troubleshooting-faq.md b/docs/12-troubleshooting-faq.md
index 9bae5bdad..ae18d5d33 100644
--- a/docs/12-troubleshooting-faq.md
+++ b/docs/12-troubleshooting-faq.md
@@ -534,7 +534,7 @@ the session card) carries a short form of it, so the pointer survives without re
of a profile a newer Chrome has opened, and that is where whatsapp-web.js keeps the WhatsApp login: every
previously linked session starts at a QR code instead of reconnecting, the log names no cause (0.23.3 and
0.23.4 log only a generic `relink_required` warning), and upgrading again does not bring the pairing back. On
-amd64 this follows a rollback from the release after 0.25.0 (Chrome for Testing 156) to 0.25.0 or earlier, and
+amd64 this follows a rollback from 0.26.0 (Chrome for Testing 156) to 0.25.0 or earlier, and
from 0.23.5 or later to 0.23.4 or earlier (146); on arm64, a rollback to an image built with an older Debian
chromium major. Restoring `sessions/` from a backup taken before the first start on the newer image keeps the
pairing (see the upgrade runbook's rollback in docs/11); without one, scan a new QR.
diff --git a/docs/14-migration-guide.md b/docs/14-migration-guide.md
index 7ecbf3b8f..f7a3b2d27 100644
--- a/docs/14-migration-guide.md
+++ b/docs/14-migration-guide.md
@@ -890,17 +890,17 @@ skips: check `pg_index.indisvalid` and drop the invalid index before building it
| Release | Change | Action |
| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `next` | Existing and older-backup LID mappings become display data; phone/LID aliases stay disabled until an actual engine mapping report. Cache-only lookup results cannot authorize an alias. Baileys preserves LIDs in message and listing identities instead of deriving them from cached phone numbers | Upgrade every reader together: older versions do not enforce the origin flag. Exact-ID grants remain available. Back up before downgrade; reversing this migration clears unreported display phone mappings so an older reader cannot authorize them |
-| `next` | The first boot rewrites every legacy `messages.type` value in one `UPDATE`, inside the transaction of the other pending migrations: on PostgreSQL about a minute per million legacy rows, with the port closed. Only a database whose conversion kept being cancelled on `0.25.0` still holds a large backlog | Count them with `SELECT count(*) FROM messages WHERE type IN ('chat', 'buttons_response', 'list_response', 'template_button_reply', 'ptt', 'vcard', 'multi_vcard')`; above a few million, run the migrations first (section 14.5), or raise `startupProbe.failureThreshold` to cover about a minute per million legacy rows (measured with twelve indexes on the table) on top of the index builds |
-| `next` | A production boot refuses a `METRICS_TOKEN` that is the `.env.example` placeholder or a weak value the other secrets are checked against (`test`, `change-me`, `changeme`, `password`, `secret`, `admin`, `demo` and a few more), trimmed and case-insensitive | Set a long random token, or unset `METRICS_TOKEN` to keep `/api/metrics` disabled (it answers `404`); there is no length floor, so a short value that is not on the list still boots |
-| `next` | Session deletion commits bounded batches (at most 2000 message rows on SQLite or 500 on PostgreSQL) before the final transaction. Current local fixtures took 23.2 s for 299,102 messages on SQLite and 11.9 s for 1,000,007 on PostgreSQL, each with about 2,000 outbox rows and 500 delivery failures. These are examples, not limits or comparisons with `0.25.0`; large outbox and failure histories can add substantially more time. Earlier batches remain committed after a later failure | Set client and proxy timeouts for the session size. Repeat DELETE to finish, or explicitly `POST /start` to keep the remaining session. Without a newer owner or explicit start, a failure after removal begins keeps the session stopped |
-| `next` | `restore.sh` stops before it copies anything, naming the key, when a path from the archive's own `.env.generated` leads out of the data directory, or into a directory the restore refills | Set that key in the environment or `./.env` to restore there; the default paths and a leftover `./uploads` restore as before |
-| `next` | A boot with `REDIS_TLS=true`, or a `REDIS_USERNAME` other than `default`, beside the built-in Redis (`REDIS_BUILTIN=true` with the bundled host) is refused, and so is an Infrastructure page save that would produce it; the container serves plain TCP and only its default user | Set `REDIS_TLS=false` and clear `REDIS_USERNAME` for the built-in Redis, or switch to an external Redis host with `REDIS_BUILTIN=false` |
-| `next` | `POST .../groups/:groupId/membership-requests/approve` and `/reject` answer `400` for a body that is a JSON list or is sent in a content type other than `application/json` or `application/x-www-form-urlencoded`; both used to act on every pending request | Send `{}` or no body to act on every pending request, and name requesters in a JSON or form body |
-| `next` | On whatsapp-web.js, `POST /api/sessions/:sessionId/pairing-code` answers `409` for a number that is the stored phone of another session of the gateway | Log that session out or delete it first, or link by QR |
-| `next` | On SQLite the first boot checks the full-text index against all stored message text and rebuilds it when they differ, so the boot takes longer on a large database while the port is closed | Allow for it in the startup probe; later boots skip the check unless `DATABASE_SYNCHRONIZE=true` |
-| `next` | The idempotency key of recurring webhook events (`message.edited`, `message.reaction`, `session.*`, `group.*`, `presence.update`) ends in a random id minted per dispatch instead of an ISO timestamp | Dedupe on the whole key; a receiver that reads its last segment as a time must stop |
-| `next` | A `conversationId` JSON pointer of an ingress route is read by RFC 6901 tokens: a trailing or doubled slash names an empty key, which the old reader skipped | Remove a stray slash from such a pointer; a delivery it no longer resolves falls back to the per-instance lane |
+| `0.26.0` | Existing and older-backup LID mappings become display data; phone/LID aliases stay disabled until an actual engine mapping report. Cache-only lookup results cannot authorize an alias. Baileys preserves LIDs in message and listing identities instead of deriving them from cached phone numbers | Upgrade every reader together: older versions do not enforce the origin flag. Exact-ID grants remain available. Back up before downgrade; reversing this migration clears unreported display phone mappings so an older reader cannot authorize them |
+| `0.26.0` | The first boot rewrites every legacy `messages.type` value in one `UPDATE`, inside the transaction of the other pending migrations: on PostgreSQL about a minute per million legacy rows, with the port closed. Only a database whose conversion kept being cancelled on `0.25.0` still holds a large backlog | Count them with `SELECT count(*) FROM messages WHERE type IN ('chat', 'buttons_response', 'list_response', 'template_button_reply', 'ptt', 'vcard', 'multi_vcard')`; above a few million, run the migrations first (section 14.5), or raise `startupProbe.failureThreshold` to cover about a minute per million legacy rows (measured with twelve indexes on the table) on top of the index builds |
+| `0.26.0` | A production boot refuses a `METRICS_TOKEN` that is the `.env.example` placeholder or a weak value the other secrets are checked against (`test`, `change-me`, `changeme`, `password`, `secret`, `admin`, `demo` and a few more), trimmed and case-insensitive | Set a long random token, or unset `METRICS_TOKEN` to keep `/api/metrics` disabled (it answers `404`); there is no length floor, so a short value that is not on the list still boots |
+| `0.26.0` | Session deletion commits bounded batches (at most 2000 message rows on SQLite or 500 on PostgreSQL) before the final transaction. Current local fixtures took 23.2 s for 299,102 messages on SQLite and 11.9 s for 1,000,007 on PostgreSQL, each with about 2,000 outbox rows and 500 delivery failures. These are examples, not limits or comparisons with `0.25.0`; large outbox and failure histories can add substantially more time. Earlier batches remain committed after a later failure | Set client and proxy timeouts for the session size. Repeat DELETE to finish, or explicitly `POST /start` to keep the remaining session. Without a newer owner or explicit start, a failure after removal begins keeps the session stopped |
+| `0.26.0` | `restore.sh` stops before it copies anything, naming the key, when a path from the archive's own `.env.generated` leads out of the data directory, or into a directory the restore refills | Set that key in the environment or `./.env` to restore there; the default paths and a leftover `./uploads` restore as before |
+| `0.26.0` | A boot with `REDIS_TLS=true`, or a `REDIS_USERNAME` other than `default`, beside the built-in Redis (`REDIS_BUILTIN=true` with the bundled host) is refused, and so is an Infrastructure page save that would produce it; the container serves plain TCP and only its default user | Set `REDIS_TLS=false` and clear `REDIS_USERNAME` for the built-in Redis, or switch to an external Redis host with `REDIS_BUILTIN=false` |
+| `0.26.0` | `POST .../groups/:groupId/membership-requests/approve` and `/reject` answer `400` for a body that is a JSON list or is sent in a content type other than `application/json` or `application/x-www-form-urlencoded`; both used to act on every pending request | Send `{}` or no body to act on every pending request, and name requesters in a JSON or form body |
+| `0.26.0` | On whatsapp-web.js, `POST /api/sessions/:sessionId/pairing-code` answers `409` for a number that is the stored phone of another session of the gateway | Log that session out or delete it first, or link by QR |
+| `0.26.0` | On SQLite the first boot checks the full-text index against all stored message text and rebuilds it when they differ, so the boot takes longer on a large database while the port is closed | Allow for it in the startup probe; later boots skip the check unless `DATABASE_SYNCHRONIZE=true` |
+| `0.26.0` | The idempotency key of recurring webhook events (`message.edited`, `message.reaction`, `session.*`, `group.*`, `presence.update`) ends in a random id minted per dispatch instead of an ISO timestamp | Dedupe on the whole key; a receiver that reads its last segment as a time must stop |
+| `0.26.0` | A `conversationId` JSON pointer of an ingress route is read by RFC 6901 tokens: a trailing or doubled slash names an empty key, which the old reader skipped | Remove a stray slash from such a pointer; a delivery it no longer resolves falls back to the per-instance lane |
| `0.25.0` | Once teardown begins (SIGTERM, SIGINT, `POST /api/infra/restart`) every request except `/api/health`, `/api/health/*`, the dashboard's HTML pages and CORS preflights answers `503` with `Connection: close`, `GET /api/infra/health` included | Probe `/api/health/live` for liveness that survives teardown, and retry a `503` once the instance is up again |
| `0.25.0` | `stop_grace_period` (Docker) and `terminationGracePeriodSeconds` (Kubernetes) go from 45 to 75 s, and a stop that runs 67 s past the shutdown delay exits with status 1 instead of 137 | Raise a pinned 45 s value to at least 75 s, plus the excess of `SHUTDOWN_DELAY_MS` over 3 s and of `WEBHOOK_SHUTDOWN_DRAIN_MS` over 5 s; on Helm upgrade with `--reset-then-reuse-values` (3.14 or later) or `-f values.yaml`, since plain `--reuse-values` keeps the 0.24.0 defaults; a container that drops all capabilities and starts as root must add `KILL` to the capabilities 0.24.0 shipped, or a stop never reaches the app; update exit-code alerts |
| `0.25.0` | `400` instead of `201` or `200` for a phone number WhatsApp reports as unregistered (Baileys; `503` when the lookup gets no answer) and for `vote-poll` with no matching option text (whatsapp-web.js) | Handle `400` (`POLL_OPTION_NOT_FOUND` carries `validOptions`) and `503` on these routes; an empty `options` list still clears a vote |
@@ -1084,7 +1084,7 @@ flowchart TD
> [!WARNING]
> A rollback across a browser major upgrade (on amd64, 0.23.5 moved Chrome for Testing from 146 to 153 and
-> the release after 0.25.0 moves it to 156; arm64 runs the chromium Debian shipped when each image was
+> 0.26.0 moves it to 156; arm64 runs the chromium Debian shipped when each image was
> built) must restore `sessions/` from a backup taken before the first start on the newer image, on both the
> full and the partial branch: a partial rollback that merges data but keeps the current `sessions/` loses
> every whatsapp-web.js login. An older Chrome silently deletes the IndexedDB of a profile a newer Chrome
diff --git a/sdk/README.md b/sdk/README.md
index 904929f3e..cead96cbc 100644
--- a/sdk/README.md
+++ b/sdk/README.md
@@ -1,6 +1,6 @@
# OpenWA SDKs
-This document describes SDK 0.7.0. Send idempotency, webhook failure redrive, message-window filters, poll choices, last-message types, and the `event.response` webhook event name require OpenWA 0.25.0 or later. The `message.receipt` and `poll.vote` webhook event names require an OpenWA release newer than 0.25.0.
+This document describes SDK 0.7.0. Send idempotency, webhook failure redrive, message-window filters, poll choices, last-message types, and the `event.response` webhook event name require OpenWA 0.25.0 or later. The `message.receipt` and `poll.vote` webhook event names require OpenWA 0.26.0 or later.
Official client libraries for [OpenWA](https://github.com/rmyndharis/OpenWA), the
open-source WhatsApp API Gateway. OpenWA is an independent project, not
diff --git a/sdk/go/README.md b/sdk/go/README.md
index f1f3e2f64..a3a854500 100644
--- a/sdk/go/README.md
+++ b/sdk/go/README.md
@@ -1,6 +1,6 @@
# OpenWA Go SDK
-This document describes SDK 0.7.0. Send idempotency, webhook failure redrive, message-window filters, poll choices, last-message types, and the `event.response` webhook event name require OpenWA 0.25.0 or later. The `message.receipt` and `poll.vote` webhook event names require an OpenWA release newer than 0.25.0.
+This document describes SDK 0.7.0. Send idempotency, webhook failure redrive, message-window filters, poll choices, last-message types, and the `event.response` webhook event name require OpenWA 0.25.0 or later. The `message.receipt` and `poll.vote` webhook event names require OpenWA 0.26.0 or later.
Idiomatic Go client for the [OpenWA](https://github.com/rmyndharis/OpenWA) WhatsApp
API Gateway. Stdlib-only (no dependencies), context-first, with typed errors and
diff --git a/sdk/java/README.md b/sdk/java/README.md
index 1745d46bb..af9557da2 100644
--- a/sdk/java/README.md
+++ b/sdk/java/README.md
@@ -1,6 +1,6 @@
# OpenWA Java SDK
-This document describes SDK 0.7.0. Send idempotency, webhook failure redrive, message-window filters, poll choices, last-message types, and the `event.response` webhook event name require OpenWA 0.25.0 or later. The `message.receipt` and `poll.vote` webhook event names require an OpenWA release newer than 0.25.0.
+This document describes SDK 0.7.0. Send idempotency, webhook failure redrive, message-window filters, poll choices, last-message types, and the `event.response` webhook event name require OpenWA 0.25.0 or later. The `message.receipt` and `poll.vote` webhook event names require OpenWA 0.26.0 or later.
Official Java client for [OpenWA](https://github.com/rmyndharis/OpenWA), the
open-source WhatsApp API Gateway. OpenWA is an independent project, not
diff --git a/sdk/javascript/README.md b/sdk/javascript/README.md
index 359b4bc9c..ece6be437 100644
--- a/sdk/javascript/README.md
+++ b/sdk/javascript/README.md
@@ -1,6 +1,6 @@
# @rmyndharis/openwa
-This document describes SDK 0.7.0. Send idempotency, webhook failure redrive, message-window filters, poll choices, last-message types, and the `event.response` webhook event name require OpenWA 0.25.0 or later. The `message.receipt` and `poll.vote` webhook event names require an OpenWA release newer than 0.25.0.
+This document describes SDK 0.7.0. Send idempotency, webhook failure redrive, message-window filters, poll choices, last-message types, and the `event.response` webhook event name require OpenWA 0.25.0 or later. The `message.receipt` and `poll.vote` webhook event names require OpenWA 0.26.0 or later.
Official JavaScript/TypeScript SDK for [OpenWA](https://github.com/rmyndharis/OpenWA), the open-source WhatsApp API Gateway. OpenWA is an independent project, not affiliated with or endorsed by WhatsApp or Meta.
diff --git a/sdk/python/README.md b/sdk/python/README.md
index 4d58cba64..d65afe74c 100644
--- a/sdk/python/README.md
+++ b/sdk/python/README.md
@@ -1,6 +1,6 @@
# rmyndharis-openwa
-This document describes SDK 0.7.0. Send idempotency, webhook failure redrive, message-window filters, poll choices, last-message types, and the `event.response` webhook event name require OpenWA 0.25.0 or later. The `message.receipt` and `poll.vote` webhook event names require an OpenWA release newer than 0.25.0.
+This document describes SDK 0.7.0. Send idempotency, webhook failure redrive, message-window filters, poll choices, last-message types, and the `event.response` webhook event name require OpenWA 0.25.0 or later. The `message.receipt` and `poll.vote` webhook event names require OpenWA 0.26.0 or later.
Official Python SDK for [OpenWA](https://github.com/rmyndharis/OpenWA), the open-source WhatsApp API Gateway. OpenWA is an independent project, not affiliated with or endorsed by WhatsApp or Meta.