notify-bridge/RELEASE_NOTES.md

v0.2.7 (2026-04-22)

Follow-up to v0.2.6: unifies the Telegram send routine across notifications and bot commands so both sides share the same aiohttp session, the same file_id caches, and the same rules for video / thumbnail URL construction. Eliminates repeat uploads that happened because single-asset sends and media groups were keyed in different caches.

Bug Fixes

• Single-asset sends now hit the asset cache — TelegramClient._get_cache_and_key treats cache_key values that look like asset UUIDs as asset-cache entries. Single-asset sends were storing file_ids in url_cache while the media-group path stored them in asset_cache, so repeat sends of the same asset never hit the cache and re-uploaded. (6de9a12)
• Notifications and commands now share the Telegram client factory — new services/telegram_send.py is the single construction path for TelegramClient: always wires the shared aiohttp session and both file_id caches. send_reply and send_media_group in commands/handler.py now delegate to the factory instead of constructing their own uncached clients, so commands reuse file_ids populated by notification dispatches (and vice versa) instead of re-uploading the same bytes. (6de9a12)
• Single rule for /video/playback vs thumbnail URLs — extracted build_asset_media_urls so the notification dispatcher's asset_to_media and the bot command handlers' common._format_assets agree on when to use the playback URL and when to use the thumbnail. Removes a subtle drift that could show stills in one path and video in the other for the same asset. (6de9a12)

---

All Commits

• 6de9a12 — fix(telegram): unify send routine across notifications and commands (alexei.dolgolyov)