fix: keep Telegram force-document payload sends on document path (openclaw#46119 thanks @thepagent)

This commit is contained in:
Frank Yang 2026-03-15 16:08:38 +08:00
parent fe98d2614d
commit 0c18527017
1 changed files with 1 additions and 0 deletions

View File

@ -39,6 +39,7 @@ Docs: https://docs.openclaw.ai
- Docs/Mintlify: fix MDX marker syntax on Perplexity, Model Providers, Moonshot, and exec approvals pages so local docs preview no longer breaks rendering or leaves stale pages unpublished. (#46695) Thanks @velvet-shark.
- Email/webhook wrapping: sanitize sender and subject metadata before external-content wrapping so metadata fields cannot break the wrapper structure. Thanks @vincentkoc.
- Node/startup: remove leftover debug `console.log("node host PATH: ...")` that printed the resolved PATH on every `openclaw node run` invocation. (#46411)
- Telegram/message send: forward `--force-document` through the `sendPayload` path as well as `sendMedia`, so Telegram payload sends with `channelData` keep uploading images as documents instead of silently falling back to compressed photo sends. (#46119) Thanks @thepagent.
## 2026.3.13