v0.3.0

telegram-menu-builder v0.3.0

Two built-in storage backends land in this release — SQL (SQLAlchemy 2.0 async) and
Redis/Valkey — both verified end-to-end against live servers.

Added

• Redis / Valkey backend — RedisStorage on redis-py, with first-class Valkey support
  (RESP-compatible: point a redis:// URL at either server, or pass a duck-typed valkey-py
  client). Native server-side TTL, namespaced keys, owns-vs-borrows client lifecycle, SCAN-based
  clear/keys (never FLUSHDB), and a lazy [redis] import. Verified end-to-end against live
  Redis 7.4.9 and Valkey 8.1.8 (fakeredis covers the default test run). Valkey is the
  recommended option. Install: pip install "telegram-menu-builder[redis]".
• SQL backend — SQLAlchemyStorage for PostgreSQL/Supabase, MySQL/MariaDB, and SQLite via
  SQLAlchemy 2.0 (async); new optional extras [postgres] and [mysql]; explicit schema management
  via create_schema()/drop_schema(). Verified end-to-end against live PostgreSQL 16 and
  MariaDB 12.3.2 (suite gated by TMB_TEST_POSTGRES_URL / TMB_TEST_MYSQL_URL).

Changed

• The [sql] extra now pins sqlalchemy[asyncio]>=2.0.30,<3.0.
• Documentation refreshed across the storage, installation, dependency-audit, and development
  guides (per-DB driver matrix incl. the pure-Python aiomysql alternative to asyncmy, UTC
  expires_at handling, portable get_stats, Docker-based integration testing). Corrected the
  documented python-telegram-bot range to >=20.0,<22.8.

Full changelog: v0.2.0...v0.3.0