• v0.2.8 d02616069d

    Notify Bridge 0.2.8
    Release / release (push) Successful in 1m58s
    Stable

    alexei.dolgolyov released this 2026-04-22 18:02:09 +03:00 | 88 commits to master since this release

    v0.2.8 (2026-04-22)

    Follow-up fix to v0.2.7's Telegram-send unification. The shared factory was
    in place, but commands and notifications were still writing into different
    cache-key namespaces — so in practice the caches never actually shared entries.

    Bug Fixes

    • Commands and notifications now share one file_id cache namespacecommon._format_assets was passing cache_key=<bare asset UUID>, while the notification dispatcher writes keys as <host>:<uuid> (derived from the URL by extract_asset_id_from_url). The two paths populated different keys for the same asset, so neither could hit the other's cached file_id and the Settings → cache-stats card only ever reflected the notification side. Dropped the explicit cache_keyTelegramClient now derives <host>:<uuid> from the URL on both paths, so one file_id cached by any dispatch or /random / /latest reply is reused by every later send. (7dae68f)

    All Commits
    • 7dae68f — fix(commands): match notification cache-key format so writes share one namespace (alexei.dolgolyov)

    Changelog

    d026160 chore: release v0.2.8
    7dae68f fix(commands): match notification cache-key format so writes share one namespace

    Downloads