| name | desktop-release-sync-landing |
| description | Use when working in the Hermes Agent CN Desktop repository on a desktop release, version bump, GitHub Release, installer packaging, release notes, or any task that changes the public desktop version. Ensures the desktop repo version is synchronized and the separate landing repository updates its website version and https://desktop.hermesagent.org.cn/latest.json manifest for the same release. |
Desktop Release Sync Landing
Overview
Use this skill whenever a desktop release is prepared, published, fixed, or documented. A release is not complete until the landing repository has been updated so /latest.json points at the same version and users can download the matching installers.
Release workflow
-
Treat package.json in this repository as the desktop version source of truth. After changing it, run pnpm run version:sync and verify Cargo.toml, Cargo.lock, tauri.conf.json, workspace package versions, READMEs, and release docs are synchronized.
-
Run the desktop checks that match the change, at minimum pnpm typecheck, pnpm test:unit, and cargo check. For release PRs also run cargo fmt --check, cargo clippy --all-features -- -D warnings, and cargo test --all-features when practical.
-
After the GitHub Release exists, get the authoritative release and asset metadata with:
gh release view v$VERSION -R Eynzof/Hermes-CN-Desktop --json tagName,publishedAt,url,assets
Do not invent size, sha256, publishedAt, or installer URLs. If the release job has not produced assets yet, stop and state that the landing sync is blocked on release assets.
-
Open or create a separate worktree/branch for Eynzof/hermes-agent-cn-desktop-landing. Prefer a codex/ branch, for example codex/update-desktop-latest-json.
-
In the landing repo, update the public release state for the same desktop version:
src/site.config.ts: set VERSION to the bare semver, for example 0.3.0.public/_worker.js: update MANIFEST.version, MANIFEST.semver, publishedAt, sourceUrl, updatedAt, asset fileName, size, sha256, versionedUrl, sourceUrl, and /releases/v... redirect entries.src/i18n/zh.ts and src/i18n/en.ts: update visible Alpha/current-version copy when it names the old version.docs/PRD.md: update the associated product version if it names the old version.
Keep https://desktop.hermesagent.org.cn/latest.json as the update manifest endpoint and https://desktop.hermesagent.org.cn/#download as the manual download entry.
-
Validate the landing change with pnpm build. Also directly exercise the worker manifest path when possible:
node -e "import('./public/_worker.js').then(async (m) => { const r = await m.default.fetch(new Request('https://desktop.hermesagent.org.cn/latest.json'), {}); console.log(r.status, await r.text()); })"
Confirm the response contains the same version, semver, asset names, sizes, hashes, and release URLs as the GitHub Release.
-
Commit and open PRs for both repositories when both changed. Mention the landing PR from the desktop release PR, or clearly state when landing did not need changes.
Guardrails
Do not close a release task by only updating this desktop repository when the public version changed. Either update landing in the same work session or explicitly report that landing sync is pending and why.
Do not change the release repository identity in landing just because GitHub redirects between Eynzof/hermes-agent-cn-desktop and Eynzof/Hermes-CN-Desktop; trust gh release view and preserve the canonical repository used by the current landing manifest unless live release metadata proves otherwise.
