Angel Engine Release
SkillDev toolsRelease Angel Engine desktop builds through the repository's GitHub Actions workflow. Use when the user asks to publish, cut, ship, tag, or release an Angel Engine desktop version, including beta/prerelease and stable releases. Enforces the required order: update desktop/package.json version first, commit it, create and push the release tag, then let or trigger the desktop release Action, and verify signed/notarized artifacts and updater metadata.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Angel Engine Release skill
What this skill tells your AI
The instructions your AI receives, as published by akarachen/angel-engine in .agents/skills/angel-engine-release/SKILL.md and read by ahel’s review.
Required Order
Never run the release workflow before the repository version state is committed and pushed.
- Decide the exact release version, for example
0.0.2or0.0.2-beta1. - Ensure the worktree is clean except intentional release edits.
- Update
desktop/package.jsonwithpnpm --dir desktop version <version> --no-git-tag-version. - Run focused checks at minimum:
npm --prefix crates/angel-engine-client-napi run build npm --prefix desktop run typecheck git diff --check - Commit the version bump:
git add desktop/package.json git commit -m "chore(desktop): release <version>" - Create the release tag from that commit:
git tag v<version> - Push the commit and tag:
git push git push origin v<version> - Only after the commit and tag are on the remote, watch the
Desktop ReleaseGitHub Action triggered by the tag. If the tag trigger does not start, then use workflow dispatch with the same version:gh workflow run desktop-release.yml --repo AkaraChen/angel-engine --ref master -f version=<version>
Guardrails
- Do not use workflow dispatch as the first release step.
- Do not release a version that is not committed in
desktop/package.json. - Do not create a tag on an unverified or dirty worktree.
- Do not push a tag before the matching commit is pushed.
- If a mistaken workflow run was started before the version commit/tag, cancel it before proceeding.
- For prereleases, keep the
v<version>tag format, such asv0.0.2-beta1. - The desktop release workflow currently publishes GitHub prereleases via
desktop/electron-builder.yml; stable-vs-prerelease policy must be changed in config before expecting a stable GitHub release.
Verification
After the Action succeeds, download the release artifacts and verify them before reporting success:
rm -rf /private/tmp/angel-engine-release-<version>
mkdir -p /private/tmp/angel-engine-release-<version>
gh release download v<version> --repo AkaraChen/angel-engine --dir /private/tmp/angel-engine-release-<version>
Required evidence:
- Release has
Angel-Engine-<version>-arm64.dmg,Angel-Engine-<version>-arm64.zip,Angel-Engine-<version>-arm64.zip.blockmap, andlatest-mac.yml. latest-mac.ymlversion equals<version>and its sha512 matches the downloaded ZIP.- DMG container passes:
xcrun stapler validate Angel-Engine-<version>-arm64.dmg codesign --verify --verbose=4 Angel-Engine-<version>-arm64.dmg spctl -a -vvv -t install Angel-Engine-<version>-arm64.dmg - App extracted from ZIP passes:
codesign --verify --deep --strict --verbose=4 "Angel Engine.app" xcrun stapler validate "Angel Engine.app" spctl -a -vvv -t exec "Angel Engine.app" - App mounted from DMG passes the same app checks.
Clean up mounted DMGs with hdiutil detach before finishing.
Signals
- GitHub stars
- 20
- Forks
- 2
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
angel-engine-release- Source
- github.com/akarachen/angel-engine