github windkh/node-red-contrib-telegrambot v18.0.0-beta.2
V18.0.0-beta.2

latest releases: v18.0.0-beta.4, v18.0.0-beta.3
pre-release6 hours ago

V18.0.0-beta.2 ๐Ÿงช

Second public beta of the V18 line (migration to node-telegram-bot-api v1.x โ€” ESM, native fetch/undici). Published under the beta dist-tag; users on latest stay on V17 and are unaffected.

npm install node-red-contrib-telegrambot@beta

Changes since beta.1

  • Bump node-telegram-bot-api floor to ^1.1.1 (#465). 1.1.1 is the lib's npm latest and is what fresh installs already resolved to; now pinned and verified. 1.1.1 fixes editMessageMedia to upload Buffers/streams/local file paths natively.
  • Simplified the editMessageMedia wrapper to a thin pass-through (the manual attach:// pre-wrap is dead code on 1.1.1) + real-library tests (#465).
  • callApi raw-API escape hatch โ€” msg.payload.type = "callApi" with method + args reaches any Bot API method without a dedicated type (#459โ€“462). See README โ†’ Calling the raw Bot API.
  • Control node: no longer forces a green "connected" status on every input (fixes the stale-green after a no-op stop).
  • Examples refreshed from manual testing (#457); fixed an out-node first-load test flake.
  • Reconciled the V17.4.15โ€“17.4.17 fixes from master into this branch.

Requirements

  • Node.js โ‰ฅ 20.

Help us test

Please run your flows (especially editMessageMedia with local files, proxy/SOCKS setups, and redeploys) and report against the test plan in #457 or a new issue. Once the GA gate clears (14-day no-P1 window, reporter retests, MIGRATION.md acceptance), beta โ†’ latest ships V18.0.0.

See MIGRATION.md. Tracking: PR #453, #448.

Don't miss a new node-red-contrib-telegrambot release

NewReleases is sending notifications on new releases.