Let a user stop a bot, and say the app is still alpha

The thinking row and the header menu both carry Stop while a bot has work open for the user anywhere: every pending or processing job of that bot in their conversations is failed as stopped, its task closed, a Stopped step recorded and one closing message posted per session, so the thread stops waiting and the bot goes idle. The handler running the job is aborted from this process through a registry, so a job stuck waiting on a model stops at once instead of on its next heartbeat, and a late face change after the abort is dropped. The release stage is now said in the app too: Settings > General reports "Cobble v0.1.5 (alpha)" next to development, and the README and RELEASING.md say what alpha means for installs.
2026-10-23 10:19:41 +01:00
parent 5beb5f3de4
commit fcad4b49d6
30 changed files with 1279 additions and 57 deletions
@@ -0,0 +1,30 @@
+import { describe, expect, test } from "bun:test";
+import versionLabel from "./version-label";
+
+describe("versionLabel", () => {
+    test("a release names its version and that it is alpha", () => {
+        expect(
+            versionLabel({
+                running: { version: "v0.1.5", mode: "production" },
+            }),
+        ).toBe("Cobble v0.1.5 (alpha)");
+    });
+
+    test("a development server says so beside the stage", () => {
+        expect(
+            versionLabel({
+                running: { version: "0.1.5", mode: "development" },
+            }),
+        ).toBe("Cobble 0.1.5 (development, alpha)");
+    });
+
+    test("a server with no usable version still names the stage", () => {
+        expect(
+            versionLabel({ running: { version: null, mode: "production" } }),
+        ).toBe("Cobble (alpha)");
+    });
+
+    test("no running version says nothing at all", () => {
+        expect(versionLabel({ running: null })).toBeNull();
+    });
+});