release v1.5.0: Telegram bot support relay #131

Merged

developer merged 2 commits from development into master 2026-06-23 16:16:04 +00:00

Conversation 1 Commits 2 Files Changed 18

+1465 -7

developer commented 2026-06-23 16:13:09 +00:00

Owner

Copy Link

Copy Source

Promote development → master for release v1.5.0.

Ships exactly one change — the Telegram bot support relay (PR #130): per-user forum topics, operator replies relayed back, info card with Block/Unblock + Clear. Bot-local (no backend, no bot-link); state on a /data volume. Off by default (TELEGRAM_SUPPORT_CHAT_ID=0).

Verified green on development (CI #548) and live on the test contour (bot log: support relay ready).

After approve: merge → tag v1.5.0 on master → prod-deploy.yaml (confirm=deploy), rolling + health-gated + auto-rollback.

Prod activation (post-deploy): PROD_TELEGRAM_SUPPORT_CHAT_ID is set; create the forum supergroup and add the bot as admin (manage topics + delete messages). Until the chat id is live the relay stays dormant.

Promote `development` → `master` for release **v1.5.0**. Ships exactly one change — the **Telegram bot support relay** (PR #130): per-user forum topics, operator replies relayed back, info card with **Block/Unblock** + **Clear**. Bot-local (no backend, no bot-link); state on a `/data` volume. **Off by default** (`TELEGRAM_SUPPORT_CHAT_ID=0`). Verified green on `development` (CI #548) and live on the test contour (bot log: `support relay ready`). **After approve:** merge → tag `v1.5.0` on master → `prod-deploy.yaml` (`confirm=deploy`), rolling + health-gated + auto-rollback. **Prod activation (post-deploy):** `PROD_TELEGRAM_SUPPORT_CHAT_ID` is set; create the forum supergroup and add the bot as admin (manage topics + delete messages). Until the chat id is live the relay stays dormant.

developer added 2 commits 2026-06-23 16:13:10 +00:00

feat(telegram): bot support relay — per-user forum topics ... 6a602aefae

Users who DM the bot anything but /start are relayed into a private
forum supergroup, one topic per user. Operators (the chat's admins)
reply in the topic and the bot copies it back to the user; an info card
opening each topic carries a Block/Unblock toggle and a Clear button.
State is a small JSON file on a new /data volume — the bot host has no
database. Off by default (TELEGRAM_SUPPORT_CHAT_ID=0): the prod bot is
unchanged until the operator sets the chat id and adds the bot as a
forum admin.

- internal/support: concurrency-safe JSON store (topic map, block list,
  relayed message ids) with field-targeted mutators and atomic save
- bot/support.go: relay both ways via copyMessage, short-TTL admin
  cache, callback buttons, per-user topic-create lock, loop guard
  (skip the bot's own posts), reopen a deleted topic on the next message
- config + compose + CI/prod-deploy: TELEGRAM_SUPPORT_CHAT_ID per
  contour + TELEGRAM_SUPPORT_STATE_DIR; bot-state named volume; /data
  pre-owned by UID 65532 so a fresh volume is writable under distroless
- docs: ARCHITECTURE §15 + decision record, FUNCTIONAL (+ru), README

Merge pull request 'feat(telegram): bot support relay — per-user forum topics' (#130) from feature/telegram-support-relay into development d86e022373

owner approved these changes 2026-06-23 16:14:13 +00:00

developer merged commit 4891216749 into master 2026-06-23 16:16:04 +00:00

Sign in to join this conversation.

Reviewers

No Reviewers

owner

Labels

No items

No Label

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

owner (Ilia) developer

No Assignees

2 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: developer/scrabble-game#131