@llblab/pi-telegram 0.18.1 → 0.18.2

package/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog
 
+## 0.18.2: setup pairing start hotfix
+
+- `[Setup]` `/telegram-setup` now updates the live in-memory config immediately after persisting the validated bot token and before starting polling. Impact: first-time setup no longer shows `Send /start...` followed by `Telegram bot is not configured`, and `/start` can be received without restarting Pi.
+
 ## 0.18.1: Windows setup transport hotfix
 
 - `[Setup]` `/telegram-setup` token validation now uses the same fallback-aware Telegram transport as normal API calls. Impact: Windows/QEMU hosts that fail native `fetch` during bot-token validation can retry through IPv4 fallback instead of failing before config is saved.

package/lib/setup.ts

@@ -172,19 +172,21 @@ export function createTelegramSetupPromptRuntime<
   return async (ctx: TContext): Promise<void> => {
     if (!ctx.hasUI || !deps.setupGuard.start()) return;
     try {
-      const nextConfig = await runTelegramSetup({
+      await runTelegramSetup({
         hasUI: ctx.hasUI,
         env: deps.env ?? process.env,
         config: deps.getConfig(),
         promptInput: (label, value) => ctx.ui.input(label, value),
         promptEditor: (label, value) => ctx.ui.editor(label, value),
         getMe: deps.getMe,
-        persistConfig: deps.persistConfig,
+        persistConfig: async (config) => {
+          await deps.persistConfig(config);
+          deps.setConfig(config);
+        },
         notify: (message, level) => ctx.ui.notify(message, level),
         startPolling: () => deps.startPolling(ctx),
         updateStatus: () => deps.updateStatus(ctx),
       });
-      if (nextConfig) deps.setConfig(nextConfig);
     } catch (error) {
       deps.recordRuntimeEvent?.("setup", error);
       throw error;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@llblab/pi-telegram",
-  "version": "0.18.1",
+  "version": "0.18.2",
   "private": false,
   "publishConfig": {
     "access": "public"