release v1.5.1: support-relay card + topic-reopen fixes #133

Merged
developer merged 3 commits from development into master 2026-06-23 16:54:01 +00:00
Owner

Promote developmentmaster for release v1.5.1 — support-relay fixes found in live prod use (PR #132).

  1. Info card name & profile link. The name is now a text_mention entity: it links the profile (reliable for username-less users the bot has seen) and stops a name beginning with / from rendering as a tappable bot command. HTML/tg:// removed.
  2. Deleted topic no longer lost to General. Telegram routes a copy aimed at a deleted topic into General with no error (confirmed in prod logs), so the bot now probes topic liveness before reuse and reopens the topic + card on deletion.

Green on development post-merge; go test -race ./platform/telegram/... + gofmt/vet clean.

After approve: merge → tag v1.5.1 on master → prod-deploy.yaml (confirm=deploy).

Promote `development` → `master` for release **v1.5.1** — support-relay fixes found in live prod use (PR #132). 1. **Info card name & profile link.** The name is now a `text_mention` entity: it links the profile (reliable for username-less users the bot has seen) and stops a name beginning with `/` from rendering as a tappable bot command. HTML/`tg://` removed. 2. **Deleted topic no longer lost to General.** Telegram routes a copy aimed at a deleted topic into General with no error (confirmed in prod logs), so the bot now probes topic liveness before reuse and reopens the topic + card on deletion. Green on `development` post-merge; `go test -race ./platform/telegram/...` + gofmt/vet clean. **After approve:** merge → tag `v1.5.1` on master → `prod-deploy.yaml` (`confirm=deploy`).
developer added 3 commits 2026-06-23 16:51:30 +00:00
fix(telegram): support card — text_mention name, no command/dead link
CI / changes (pull_request) Successful in 3s
CI / unit (pull_request) Successful in 10s
CI / integration (pull_request) Successful in 17s
CI / ui (pull_request) Has been skipped
CI / gate (pull_request) Successful in 0s
CI / deploy (pull_request) Successful in 1m19s
bb18dc362b
The topic info card built the profile link as `tg://user?id=`, which
clients render as dead text for a user they don't already know (the
test-vs-prod difference an operator saw), and it put the raw display
name through HTML — so a name starting with "/" was auto-detected as a
tappable bot command that fired when tapped.

Render the card with message entities instead: the display name is
covered by a `text_mention` entity (the reliable way to mention a
username-less user the bot has already seen — it messaged the bot),
which links the profile AND, because the name sits inside an entity,
suppresses the "/command" and "@mention" auto-detection on it. Drop the
HTML parse mode and the tg:// link. Entity offsets are UTF-16.
fix(telegram): reopen a deleted support topic instead of losing it to General
CI / changes (pull_request) Successful in 2s
CI / unit (pull_request) Successful in 9s
CI / integration (pull_request) Successful in 16s
CI / ui (pull_request) Has been skipped
CI / gate (pull_request) Successful in 0s
CI / deploy (pull_request) Successful in 1m18s
fc1715128e
Telegram silently routes a copyMessage aimed at a deleted forum topic
into the chat's General topic with NO error, so the bot's error-based
recreate never fired — the user's next message landed in General with no
card. Confirmed against the prod bot logs: a relay after a topic deletion
logged neither "relay to topic failed" nor "topic gone, reopening".

Probe topic liveness before reusing it: re-applying the info card's reply
markup is a no-op that errors only when the card (hence the topic) is
gone, so the bot detects the deletion and reopens the topic + card rather
than relying on the (absent) copy error. The post-copy recreate stays as
a race backstop.
Merge pull request 'fix(telegram): support relay — text_mention card + reopen deleted topic' (#132) from feature/telegram-support-card-mention into development
CI / changes (push) Successful in 2s
CI / unit (push) Successful in 10s
CI / integration (push) Successful in 17s
CI / ui (push) Has been skipped
CI / changes (pull_request) Successful in 2s
CI / gate (push) Successful in 0s
CI / deploy (push) Successful in 1m17s
CI / unit (pull_request) Successful in 10s
CI / integration (pull_request) Successful in 17s
CI / ui (pull_request) Has been skipped
CI / gate (pull_request) Successful in 0s
CI / deploy (pull_request) Has been skipped
10264e10c8
owner approved these changes 2026-06-23 16:53:00 +00:00
developer merged commit 7923b3cc09 into master 2026-06-23 16:54:01 +00:00
Sign in to join this conversation.
No Reviewers
No Label
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: developer/scrabble-game#133