Sam & Claude
16911c5ac9
Some checks are pending
Docker Build and Publish / build-amd64 (push) Waiting to run
Docker Build and Publish / build-arm64 (push) Waiting to run
Docker Build and Publish / merge (push) Blocked by required conditions
Lint (ruff + ty) / ruff + ty diff (push) Waiting to run
Lint (ruff + ty) / ruff enforcement (blocking) (push) Waiting to run
Lint (ruff + ty) / Windows footguns (blocking) (push) Waiting to run
Nix / nix (macos-latest) (push) Waiting to run
Nix / nix (ubuntu-latest) (push) Waiting to run
Tests / test (1) (push) Waiting to run
Tests / test (2) (push) Waiting to run
Tests / test (3) (push) Waiting to run
Tests / test (4) (push) Waiting to run
Tests / test (5) (push) Waiting to run
Tests / test (6) (push) Waiting to run
Tests / save-durations (push) Blocked by required conditions
Tests / e2e (push) Waiting to run
Typecheck / typecheck (apps/bootstrap-installer) (push) Waiting to run
Typecheck / typecheck (apps/desktop) (push) Waiting to run
Typecheck / typecheck (apps/shared) (push) Waiting to run
Typecheck / typecheck (ui-tui) (push) Waiting to run
Typecheck / typecheck (web) (push) Waiting to run
Telegram Web doesn't support Bot API 10.1 sendRichMessage, so gateway startup/shutdown/restart notifications rendered as 'This message is not supported on the web version of Telegram.' Root cause: TelegramAdapter.send() uses sendRichMessage for every non-empty message. Lifecycle notifications are plain text and gain nothing from rich rendering. Fix: - telegram.py: add 'skip_rich' metadata flag to _should_attempt_rich() - run.py: set skip_rich=True on all 4 lifecycle notification paths (shutdown→active chats, shutdown→home channel, startup→home, restart→active chat) Lifecycle notifications now use plain sendMessage. All other messages continue using sendRichMessage for rich rendering. Also: sync colibri_bridge.in template from live OSA deployment. |
||
|---|---|---|
| .. | ||
| freebsd | ||
| homebrew | ||