mirror of
https://github.com/dreamhunter2333/cloudflare_temp_email.git
synced 2026-09-08 17:08:59 +08:00
Dream HunterandClaude Opus 4.7
296ddb8619
- Upgrade version to 1.8.0 in all package.json files - Add cf-temp-mail-release-notify skill with MarkdownV2 Telegram posting - Optimize docs_deploy.yml to auto-trigger on Tag Build CI completion - Add v1.8.0 placeholder in CHANGELOG.md and CHANGELOG_EN.md Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
1.8 KiB
1.8 KiB
name, description
| name | description |
|---|---|
| cf-temp-mail-release-notify | Announce a cloudflare_temp_email GitHub release to the project's Telegram channel topic. Use when the user asks to notify/announce/broadcast a release to Telegram, push release notes to the channel, or send a release to the topic after running cf-temp-mail-release. Posts bilingual (中文 + English) changelog excerpts plus the release URL. |
Release Notify Workflow
Post an existing GitHub release's notes to the project's Telegram channel topic.
Prerequisites
config.jsonexists in this skill directory withtoken,chat_id,message_thread_id(gitignored, never commit).ghCLI authenticated.uvinstalled (brew install uv/curl -LsSf https://astral.sh/uv/install.sh | sh). Script uses PEP 723 inline metadata;uvauto-installs deps.
Steps
- Resolve tag: If the user didn't give one, use the latest release:
gh release list --limit 1 --json tagName --jq '.[0].tagName'. - Run the script:
The script fetches the release via
uv run scripts/send_release_to_telegram.py vX.Y.Zgh, splits the body into zh/en sections, strips PR collapsibles and the cache-clearing link, truncates to fit Telegram's 4096-char limit, and posts to the configuredchat_id+message_thread_id. - Verify: The script prints
ok: message_id=<id>on success. Report the message id.
Notes
- Message uses
parse_mode: MarkdownV2; all content is escaped (viamd_escape) to avoid parse errors on reserved chars_ * [ ] ( ) ~ \> # + - = | { } . !`. - Only the zh/en changelog sections are posted. PRs list and the cache-clearing discussion link are stripped to keep the message concise.
- For very long release bodies, zh and en are each truncated to ~half of the 3500-char body budget.