v0.6.0 — reliability + remote control #5
b1rdmaniaAnnotations
10 errors and 2 warnings
|
src/channels/telegram.test.ts > TelegramChannel > text message handling > falls back to user ID when name and username missing:
src/channels/telegram.ts#L364
TypeError: this.bot.api.setMyCommands is not a function
❯ TelegramChannel.connect src/channels/telegram.ts:364:8
❯ src/channels/telegram.test.ts:336:21
|
|
src/channels/telegram.test.ts > TelegramChannel > text message handling > falls back to username when first_name missing:
src/channels/telegram.ts#L364
TypeError: this.bot.api.setMyCommands is not a function
❯ TelegramChannel.connect src/channels/telegram.ts:364:8
❯ src/channels/telegram.test.ts:321:21
|
|
src/channels/telegram.test.ts > TelegramChannel > text message handling > extracts sender name from first_name:
src/channels/telegram.ts#L364
TypeError: this.bot.api.setMyCommands is not a function
❯ TelegramChannel.connect src/channels/telegram.ts:364:8
❯ src/channels/telegram.test.ts:307:21
|
|
src/channels/telegram.test.ts > TelegramChannel > text message handling > skips command messages (starting with /):
src/channels/telegram.ts#L364
TypeError: this.bot.api.setMyCommands is not a function
❯ TelegramChannel.connect src/channels/telegram.ts:364:8
❯ src/channels/telegram.test.ts:295:21
|
|
src/channels/telegram.test.ts > TelegramChannel > text message handling > only emits metadata for unregistered chats:
src/channels/telegram.ts#L364
TypeError: this.bot.api.setMyCommands is not a function
❯ TelegramChannel.connect src/channels/telegram.ts:364:8
❯ src/channels/telegram.test.ts:277:21
|
|
src/channels/telegram.test.ts > TelegramChannel > text message handling > delivers message for registered group:
src/channels/telegram.ts#L364
TypeError: this.bot.api.setMyCommands is not a function
❯ TelegramChannel.connect src/channels/telegram.ts:364:8
❯ src/channels/telegram.test.ts:249:21
|
|
src/channels/telegram.test.ts > TelegramChannel > connection lifecycle > disconnects cleanly:
src/channels/telegram.ts#L364
TypeError: this.bot.api.setMyCommands is not a function
❯ TelegramChannel.connect src/channels/telegram.ts:364:8
❯ src/channels/telegram.test.ts:228:21
|
|
src/channels/telegram.test.ts > TelegramChannel > connection lifecycle > registers error handler on connect:
src/channels/telegram.ts#L364
TypeError: this.bot.api.setMyCommands is not a function
❯ TelegramChannel.connect src/channels/telegram.ts:364:8
❯ src/channels/telegram.test.ts:219:21
|
|
src/channels/telegram.test.ts > TelegramChannel > connection lifecycle > registers command and message handlers on connect:
src/channels/telegram.ts#L364
TypeError: this.bot.api.setMyCommands is not a function
❯ TelegramChannel.connect src/channels/telegram.ts:364:8
❯ src/channels/telegram.test.ts:200:21
|
|
src/channels/telegram.test.ts > TelegramChannel > connection lifecycle > resolves connect() when bot starts:
src/channels/telegram.ts#L364
TypeError: this.bot.api.setMyCommands is not a function
❯ TelegramChannel.connect src/channels/telegram.ts:364:8
❯ src/channels/telegram.test.ts:191:21
|
|
ci
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
ci
The process '/usr/bin/git' failed with exit code 128
|