alvin-bot 5.1.2 → 5.1.3
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 +14 -9
- package/dist/providers/runtime-header.js +18 -12
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -2,23 +2,28 @@
|
|
|
2
2
|
|
|
3
3
|
All notable changes to Alvin Bot are documented here.
|
|
4
4
|
|
|
5
|
-
## [5.1.
|
|
5
|
+
## [5.1.3] — 2026-05-13
|
|
6
|
+
|
|
7
|
+
### Stability hardening — runtime-header fallbacks
|
|
6
8
|
|
|
7
|
-
|
|
9
|
+
Small robustness pass on the runtime-header block that the bot uses to introduce itself. If the embedded version or install-path can't be resolved for any reason, those lines are now simply omitted instead of literally telling the model "I am version unknown". Node version and platform are still emitted so the bot can still describe its environment.
|
|
8
10
|
|
|
9
|
-
|
|
11
|
+
### Cleaner release notes for global users
|
|
10
12
|
|
|
11
|
-
|
|
13
|
+
Polished the release notes that surface inside the Telegram `/update` summary so non-technical users see a clear, English summary of what changed. No behaviour changes.
|
|
14
|
+
|
|
15
|
+
## [5.1.2] — 2026-05-13
|
|
12
16
|
|
|
13
|
-
|
|
17
|
+
### Bot now reports its real version after every update
|
|
14
18
|
|
|
15
|
-
|
|
19
|
+
If you asked the bot "what version are you?", it used to look up the version that someone had written into the project documentation by hand — which went out of date the moment a new release shipped. The bot would happily say "I'm v4.19.2" even though the running process was already on something newer.
|
|
16
20
|
|
|
17
|
-
|
|
21
|
+
Now the bot reads its version straight from the running code on disk, every single turn, regardless of provider (Claude SDK, Codex CLI, Groq, Gemini, OpenAI, Ollama, OpenRouter, NVIDIA NIM). It also includes its install path, Node version, and platform — so when something goes wrong you can ask the bot to introduce itself and get an honest answer.
|
|
18
22
|
|
|
19
|
-
###
|
|
23
|
+
### What does this mean for you
|
|
20
24
|
|
|
21
|
-
|
|
25
|
+
- Update via Telegram `/update` and the bot will pick up the new version on the next restart.
|
|
26
|
+
- Ask the bot in chat "which version are you running?" — the answer is now grounded in reality, not in a docs file that might be stale.
|
|
22
27
|
|
|
23
28
|
## [5.1.1] — 2026-05-13
|
|
24
29
|
|
|
@@ -24,16 +24,22 @@ function getInstallPath() {
|
|
|
24
24
|
}
|
|
25
25
|
export function buildRuntimeHeader() {
|
|
26
26
|
const installPath = getInstallPath();
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
|
|
31
|
-
|
|
32
|
-
`
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
|
|
38
|
-
|
|
27
|
+
const lines = ["<bot_runtime>"];
|
|
28
|
+
// Only emit `version:` when we actually know it. Emitting "unknown" is worse
|
|
29
|
+
// than emitting nothing — the model will dutifully report "I am version
|
|
30
|
+
// unknown" instead of falling back to a reasonable hedge.
|
|
31
|
+
if (BOT_VERSION && BOT_VERSION !== "unknown") {
|
|
32
|
+
lines.push(`version: ${BOT_VERSION}`);
|
|
33
|
+
}
|
|
34
|
+
if (installPath && installPath !== "(unknown)") {
|
|
35
|
+
lines.push(`install_path: ${installPath}`);
|
|
36
|
+
}
|
|
37
|
+
if (process.version) {
|
|
38
|
+
lines.push(`node: ${process.version}`);
|
|
39
|
+
}
|
|
40
|
+
if (process.platform) {
|
|
41
|
+
lines.push(`platform: ${process.platform}`);
|
|
42
|
+
}
|
|
43
|
+
lines.push("</bot_runtime>", "", "When asked about your version, identity, or install path, use the values", "in <bot_runtime> above. Ignore any version number that appears in the", "project documentation (CLAUDE.md, README) — that file may be stale.");
|
|
44
|
+
return lines.join("\n");
|
|
39
45
|
}
|