Commit Graph
16 Commits
Author SHA1 Message Date
翅膀 7882701e1f fix(telegram): keep completed commands claimed
Redelivery after a completed write must never post another comment.
Keep completion claims despite reply failures, scope updates per bot
and only issue account-login links in private chats.
2026-10-23 23:23:11 +08:00
翅膀 8b10b98880 fix(telegram): honor the author emoji toggle
The author marker must obey the group emoji preference just like
formatter-added decoration.
2026-10-23 23:23:10 +08:00
翅膀 7a76cac8a1 fix(telegram): clamp visible html characters
Telegram counts visible characters, not HTML source bytes.
Truncate without splitting tags, entities or surrogate pairs.
2026-10-23 23:23:08 +08:00
翅膀 93650141f7 fix(telegram): render hard breaks as newlines
Telegram HTML does not support br tags. Render Markdown hard breaks
as plain newlines so otherwise valid messages are accepted.
2026-10-23 23:23:06 +08:00
翅膀 dd45e13cb1 fix(telegram): keep editable messages as text
Guessing photo versus text from message content makes later edits
use the wrong API and a smaller caption budget. Always send text
and use the avatar as a link preview.
2026-10-23 23:23:05 +08:00
翅膀 867d2af6ac fix(telegram): report unreadable send results
An unreadable successful response may already have sent the message.
Report an explicit uncertain result instead of retrying a create
without an idempotency key or pretending it succeeded.
2026-10-23 23:23:03 +08:00
翅膀 b212989c05 fix(telegram): honor nested rate-limit delays
Telegram places retry_after inside parameters, not at the top level.
Read that value and defer long waits to the delivery queue.
2026-10-23 23:23:02 +08:00
翅膀 03021f7c2b fix(telegram): bound individual api requests
Bound individual platform calls so they cannot outlive the lock
protecting a message update or stall a whole delivery invocation.
2026-10-23 23:22:58 +08:00
翅膀 0bf18fe2ca fix(telegram): always verify webhook secrets
Webhook verification must not silently disable itself when the
optional secret is absent. Derive a stable secret from the bot
token and reject callbacks when verification is unavailable.
2026-10-23 23:22:57 +08:00
RhenCloud 2e89c79e9c fix(telegram): render rich header title as plain text 2026-09-13 13:13:09 +08:00
RhenCloud 9899cd01bf fix(telegram): render HTML with markdown-it and strip HTML from Discord bodies 2026-08-24 22:51:26 +08:00
RhenCloud 7ac7bb7958 fix(render): link title head to the event object URL 2026-08-15 18:25:23 +08:00
RhenCloud 3dce114cec feat(groups): optional forge source label in message footers
- Group.forgeLabel (default off, editable per group in the console) shows the
  source forge on every message the group's routes dispatch
- Discord embed footer: forge name next to the repo + the site's favicon as
  icon_url (Gitea instance's own favicon from its origin)
- Telegram footer: hyperlinked site name (GitHub or Gitea hostname); custom
  webhooks render a plain 'Custom' label
- forgeInfo() derives branding from event.provider + repository.html_url;
  dispatch attaches it to the NeutralMessage like mentionRoleIds
- validateGroups accepts forgeLabel booleans; GroupEditor gains the toggle
- tests: forgeInfo unit, discord/telegram footer render, dispatch on/off
- docs: groups.md + message-format.md (en/zh), config.example.yaml, AGENTS.md
- fix: wrangler.jsonc compatibility_date was an incomplete '2026-'
2026-08-14 08:10:04 +08:00
RhenCloud a5324fb0ea fix(formatters): localize PR buttons, cap oversized content, dedupe status logic
- PR merge/close button labels now follow the group language (actions.merge/close)
  instead of hardcoded Chinese
- clamp content to Discord embed limits (title 256, description 4096, field value
  1024, 25 fields) in formatters plus a render-layer safety net; Telegram gets a
  tag-safe 4096-char cap (capHtml closes dangling tags)
- raise commit subject truncation from 72 to 200 chars (MAX_COMMIT_SUBJECT)
- extract workflowStatus/workflowRunStatus/statusColorKey helpers shared by
  check_run/check_suite/workflow_run/workflow_job
- dedupe deployment ref/sha fields via addDeploymentRefFields
- commit_comment without a commit id uses title_plain (no dangling ???????)
- tag pushes now report 'Tag created'; zh push title includes the {ref}
- sender profile link derives from the repo's forge origin instead of github.com
- group webhook log emoji injected via emojiPrefix, removed from locale files
- dispatchEvent accepts preloaded groups (single KV read per webhook)
- webhook 401 logs distinguish 'secret not configured' from 'invalid signature'
2026-08-14 07:41:19 +08:00
RhenCloud dfb65ef70d fix: link only the repo head in message titles, keep the subject plain 2026-08-13 19:18:55 +08:00
RhenCloud b139712a91 feat: migrate to Nuxt 4 (Nitro) and Tailwind CSS v3 2026-08-13 17:43:33 +08:00