node-telegram-bot-api 2.3.0-rc0

on Node.js NPM

Session storage

• Added S3SessionStorage (exported from the core node-telegram-bot-api): a
  durable, cross-instance session backend for any S3-compatible object store
  (AWS S3, Cloudflare R2, MinIO, DigitalOcean Spaces), speaking the S3 REST API
  directly over fetch with AWS Signature V4 signing. Core and runtime-agnostic
  (Node 19+, Bun, Deno, Workers, edge); fetch and crypto are injectable, so
  Node 18 can supply node:crypto's webcrypto. It has no per-object TTL - use
  a bucket lifecycle rule on the prefix. Validated against the AWS SigV4 example
  vector, the aws4 reference signer, and live MinIO / RustFS / Bun S3 servers.

Uploads

• InputFile uploads no longer throw ReferenceError: crypto is not defined on
  Node 18: the multipart boundary is now built without the global WebCrypto
  (which Node exposes unflagged only from v19), so uploads work across the full
  supported Node 18.2+ range (#1378).

Full diff: v2.2.0...v2.3.0-rc0