Free, Open Source, Self-Hosted WhatsApp API Gateway
TypeScript apibotgatewayself-hostedwhatsappwhatsapp-apiwhatsapp-automationwhatsapp-botwhatsapp-gatewaywhatsapp-gateway-apiwhatsapp-webwhatsapp-web-api
Merge pull request #1633 from rmyndharis/docs/wwebjs-call-events
Yudhi Armyndhariscd6761b47d32
diff --cc CHANGELOG.mdindex da0aba876,69df15fb2..67f858498--- a/CHANGELOG.md+++ b/CHANGELOG.md@@@ -19,11 -19,11 +19,15 @@@ and this project adheres to [Semantic V- Session leases on PostgreSQL compare as instants across nodes in different time zones and across a daylight-saving change.- Live WebSocket sockets are re-validated against the API-key table once a minute, so a key deleted, revoked, expired or narrowed on another node or by a direct database write drops its sockets there too, and a socket that connected while its key was being revoked no longer keeps that authorization for the life of the connection ([#1625](https://github.com/rmyndharis/OpenWA/issues/1625)).- A WebSocket subscribe whose socket is evicted while it is in flight no longer registers its rooms after the disconnect.+- The dashboard no longer opens a QR modal after a start that left the session without an engine.+- A failed start in the dashboard that left no engine shows the gateway's error in a toast.+- The dashboard closes a session's QR modal when the session fails, or disconnects with no engine left, instead of leaving it spinning.+- The dashboard disables a session's Start and Reconnect buttons while its start request is in flight.+ ### Documentation++ - The docs, the README, the OpenAPI field descriptions and the dashboard's auto-reject hint mark call events, call rejection and `autoRejectCalls` as Baileys only: on current WhatsApp Web builds whatsapp-web.js no longer detects a ringing call ([#1118](https://github.com/rmyndharis/OpenWA/discussions/1118)). Thanks @etondeengole for the report.+### Upgrade notes (behavior changes)- PostgreSQL deployments: the data connection issues `SET TIME ZONE 'UTC'` per connection and verifies the result at boot. A deployment where that cannot hold (a pooler that drops session state) now fails to start, naming the effective zone; set the default instead with `ALTER DATABASE "<database>" SET TimeZone='UTC'`. SQLite deployments, and any gateway already running in UTC, are unaffected and no data moves.