node-red-contrib-telegrambot 18.0.2

V18.0.2

on Node.js NPM

V18.0.2

Patch release fixing SOCKS proxy support under V18.

Fixed

• SOCKS proxy bots failed to connect on V18 (#472, by @Alexey-Tsarev). Node-RED stores the SOCKS port config field as a string, but V18's transport path (fetch-socks → socks) validates that the port is a number, so it threw:

  Invalid SOCKS proxy details were provided (EFATAL / fetch failed)

  …and the bot never connected. buildDispatcherOptions now coerces the port with Number(...). V17's socks-proxy-agent tolerated string ports, so this only affected V18. If you use a SOCKS proxy, this restores connectivity.

Upgrade

cd ~/.node-red
npm install node-red-contrib-telegrambot@latest
node-red-restart

Thanks to @Alexey-Tsarev for the fix and the clear diagnosis.