Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

docs(changelog): cover a whole batch of unreadable ingress rows

Yudhi Armyndharised230fb89983
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 7b3dd7277..d18672191 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -61,7 +61,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
- Uninstalling a plugin hands the chats it had taken over back to the bot, so other plugins are no longer silent there.
- A `CORS_ORIGINS` entry written with a path or a trailing slash is used as the origin it names, and a warning at boot lists it, where it matched no `Origin` header.
- Index ingress dead letters by delivery id, so the reconciler's per-delivery checks stop scanning every dead letter of an instance; the first boot builds the index.
-- Replay stranded ingress events past one whose stored payload is not valid JSON, instead of failing every sweep on it.
+- Replay stranded ingress events past one whose stored payload is not valid JSON, instead of failing every sweep on it, and past a whole batch of such rows, which no longer head every sweep.
- Replay stranded webhook deliveries and redrive ingress dead letters past a row whose stored payload is not valid JSON, instead of failing every pass on it.
- Hand a chat back to the bot when the plugin instance that took it over is deleted, instead of silencing every other plugin on it.
- Keep the sessions of a plugin's other enabled instances active when creating, disabling or deleting a session-scoped instance retires an operator-set `*`.