V18.0.0-beta.3
Pre-release
Pre-release
·
3 commits
to migration/ntba-v1
since this release
V18.0.0-beta.3 🧪
Third public beta of the V18 line. Published under the beta dist-tag; users on latest stay on V17 and are unaffected.
npm install node-red-contrib-telegrambot@beta
Change since beta.2
- Per-bot undici dispatcher (#466 / #465). The dispatcher (plain undici
Agent, orfetch-sockssocksDispatcherfor SOCKS) is now scoped to each bot via lib v1.1.1'srequest.fetchOptions.dispatcher, instead of the process-globalglobalThis[undici.globalDispatcher.1]symbol used in beta.1/beta.2. This restores per-bot pool/proxy isolation (eachtelegram botconfig node gets its own pool again, like V17) and removes the process-global side effect. The #442 keep-alive recovery defence is now genuinely per-bot, and the previous dispatcher is closed on re-instantiation so pools don't leak.
No flow/config changes — proxy and address-family settings work exactly as before.
Requirements
- Node.js ≥ 20.
Help us test
Especially welcome: SOCKS proxy setups and multi-bot instances (multiple telegram bot config nodes), plus redeploys. Report against #457 or a new issue.
See MIGRATION.md. Tracking: PR #453, #448.