Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

docs: correct the call rejection note and the patch write scope

Yudhi Armyndharis9eb5ca810086
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 3162f9f11..51e550348 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -263,7 +263,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
- Update only the supplied fields on `PUT /api/sessions/{sessionId}/templates/{id}` and answer 404 for a template deleted meanwhile, where an overlapping edit was undone or the template came back.
- Report a status whose row was removed while its media was written as not stored, and delete its file.
- Accept an empty `url` next to `base64` in status posts and media conversion.
-- Write each patched dependency file to a temporary file and rename it over the original, so a write that fails part-way, such as on a full disk, leaves the file unchanged; a best-effort patch is then skipped, and any other install fails instead of keeping a truncated file.
+- Write each dependency file the postinstall scripts rewrite, except the whatsapp-web.js diff patch, to a temporary file and rename it over the original, so a write that fails part-way, such as on a full disk, leaves the file unchanged; a best-effort patch is then skipped, and any other install fails instead of keeping a truncated file.
- Keep the `latest` and `X.Y` image tags from moving to an older release when an older tag is released or re-run.
- Create the GitHub Release from a notes file, so a CHANGELOG section containing a line that is exactly `EOF` no longer breaks it.
- Mirror the PHP SDK to `openwa-php` only from `main` and only while its content matches `main`, so a manual run from another branch or a re-run of an older push no longer replaces a newer mirror.
diff --git a/docs/06-api-specification.md b/docs/06-api-specification.md
index ccf0cb8ab..058716249 100644
--- a/docs/06-api-specification.md
+++ b/docs/06-api-specification.md
@@ -6735,7 +6735,7 @@ Generate a shareable WhatsApp call link.
Reject a currently ringing incoming call. **Baileys only**: the whatsapp-web.js engine answers `501`. Only a live call can be rejected: the id is valid while the call rings (a short server-side cache); afterwards it expires.
-A failed rejection can be retried only while the same call is still ringing; a call that ends or rings again during the attempt is not restored. If the call is accepted, rejected or missed while a rejection is pending, that outcome is reported once as the call's `call.accepted`, `call.rejected` or `call.missed` event, even when the rejection then fails or times out. A completed rejection that no longer belongs to the current call, because it ended or the connection was cleared meanwhile, reports nothing.
+A failed rejection can be retried only while the same call is still ringing; a call that ends or rings again during the attempt is not restored. If the call is accepted, rejected or missed while a rejection is pending, that outcome is reported once as the call's `call.accepted`, `call.rejected` or `call.missed` event, even when the rejection then fails or times out. A rejection that completes after a `terminate` for the same call still reports `call.rejected`. One that no longer belongs to the current call, because the connection was cleared or another caller took the call id meanwhile, reports nothing.
**Auth:** API key (OPERATOR)
diff --git a/docs/15-project-roadmap.md b/docs/15-project-roadmap.md
index f127b7683..a2693cad7 100644
--- a/docs/15-project-roadmap.md
+++ b/docs/15-project-roadmap.md
@@ -761,9 +761,9 @@ For a stable tag, `release-tags` reads which release `X.Y` and `latest` serve on
a channel alone when it already serves a newer one, so releasing a patch to an older line or re-running an
old tag never moves a channel backwards; the exact `X.Y.Z` tag is still applied. A channel it cannot read
fails the release rather than counting as absent; only the registry's own "manifest unknown" answer does.
-`verify-published` then expects only the tags `release-tags` selected. It also decides whether the GitHub
-Release is marked Latest: only when this release took every `latest` channel, never for a prerelease or a
-patch to an older line.
+`verify-published` then expects only the tags `release-tags` selected. `release-tags` also decides whether
+the GitHub Release is marked Latest: only when this release took every `latest` channel, never for a
+prerelease or a patch to an older line.
### When a gate fails