alvin-bot 5.1.3 → 5.1.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,14 @@
|
|
|
2
2
|
|
|
3
3
|
All notable changes to Alvin Bot are documented here.
|
|
4
4
|
|
|
5
|
+
## [5.1.4] — 2026-05-15
|
|
6
|
+
|
|
7
|
+
### No more false "errors are climbing" health alerts
|
|
8
|
+
|
|
9
|
+
The bot has a self-health monitor that watches how many error lines show up in its logs over the last 24 hours and warns you if the count keeps creeping up. One harmless, self-correcting event was confusing it: when a message can't be sent with rich formatting, the bot quietly retries it as plain text and the message still gets delivered. That retry was being written to the error log, so the health monitor counted every single one as a real error — producing a slow, fake "your error rate is rising" alarm even though nothing was actually wrong.
|
|
10
|
+
|
|
11
|
+
That benign retry is now logged as normal activity instead of as an error, so the 24-hour error trend reflects reality. Message delivery itself is unchanged — this only fixes where the event is recorded.
|
|
12
|
+
|
|
5
13
|
## [5.1.3] — 2026-05-13
|
|
6
14
|
|
|
7
15
|
### Stability hardening — runtime-header fallbacks
|
|
@@ -35,7 +35,7 @@ async function sendWithMarkdownFallback(api, chatId, text) {
|
|
|
35
35
|
catch (err) {
|
|
36
36
|
if (!isTelegramParseError(err))
|
|
37
37
|
throw err;
|
|
38
|
-
console.
|
|
38
|
+
console.log(`[subagent-delivery] Markdown parse failed, retrying as plain text`);
|
|
39
39
|
await api.sendMessage(chatId, text);
|
|
40
40
|
}
|
|
41
41
|
}
|