发布的最后一步调用部署挂钩，让官网 shellrs.com 重新构建：官网的下载页和更新日志在构建时读更新清单，所以放在清单上传、清 CDN 缓存之后；挂钩地址是 release 环境的 secret SITE_DEPLOY_HOOK

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

.github/workflows/release.yml

@@ -8,7 +8,8 @@
 #            dl.shellrs.com, creates the GitHub release, and only then
 #            replaces the channel's manifest, which is what clients follow;
 #            the manifest lists the GitHub release as each package's
-#            second address
+#            second address; last, it has Cloudflare rebuild shellrs.com,
+#            whose download page and changelog read that manifest
 #
 # A tag with a pre-release (v0.3.0-beta.1) goes to the beta channel only. A
 # stable release also becomes the beta channel's, unless beta is ahead.
@@ -22,7 +23,7 @@
 #               (base64), APPLE_API_KEY_ID, APPLE_API_ISSUER
 #   environment `release`: MINISIGN_SECRET_KEY, MINISIGN_PASSWORD,
 #               R2_ACCOUNT_ID, R2_ACCESS_KEY_ID, R2_SECRET_ACCESS_KEY,
-#               R2_BUCKET, CF_ZONE_ID, CF_API_TOKEN
+#               R2_BUCKET, CF_ZONE_ID, CF_API_TOKEN, SITE_DEPLOY_HOOK
 name: release
 
 on:
@@ -335,3 +336,8 @@ jobs:
           curl -fsS -X POST "https://api.cloudflare.com/client/v4/zones/$CF_ZONE_ID/purge_cache" \
             -H "Authorization: Bearer $CF_API_TOKEN" -H "Content-Type: application/json" \
             --data "$files"
+      # After the purge: the site's build reads the manifests from dl.shellrs.com.
+      - name: Rebuild shellrs.com
+        env:
+          SITE_DEPLOY_HOOK: ${{ secrets.SITE_DEPLOY_HOOK }}
+        run: curl -fsS -X POST "$SITE_DEPLOY_HOOK"