catalog: bump telegram-notify to v1.1.2

Bumps the pinned sha to the v1.1.2 release and version to 1.1.2.
v1.1.2 fixes the codex-telegram-notify attribution/link and suppresses
duplicate lifecycle notifications for Telegram-origin sessions, while
preserving existing subagent/smart-approval filtering.
This commit is contained in:
madpower2000
2026-09-27 01:10:32 +03:00
committed by Teknium
parent ca01cd4ef7
commit cb5fcb0cd5

View File

@@ -1,11 +1,11 @@
name: telegram-notify
repo: https://github.com/madpower2000/hermes-telegram-notify
sha: 78a3c297d5b0a8f2489eb672e814a38f5d2fa210
sha: 71d0af9d8916420e4089104fcbf0c513b7870b0c
description: >-
Remote Telegram lifecycle notifications for the main Hermes agent: turn
start, completion with a bounded final answer, interruption/failure, and
user-facing approval requests. Suppresses subagent and automatic/smart-approval
noise. Outbound-only, no input channel. Disclosure — enabled by default once installed and
user-facing approval requests. Suppresses subagent, Telegram-origin lifecycle,
and automatic/smart-approval noise. Outbound-only, no input channel. Disclosure — enabled by default once installed and
reuses the core Telegram gateway's TELEGRAM_BOT_TOKEN and TELEGRAM_HOME_CHANNEL when present,
so each main-agent turn's final answer (up to 3,200 chars) and approval-request command text
(up to 700 chars) from CLI, Desktop and any gateway platform are sent to api.telegram.org for
@@ -15,7 +15,7 @@ tier: community
category: automation
requires_hermes: ">=0.21.5"
docs_url: https://github.com/madpower2000/hermes-telegram-notify
version: "1.1.1"
version: "1.1.2"
platforms: []
capabilities:
provides_tools: []