releaselisted

# Release Skill Use this skill when preparing, publishing, or verifying an Ein installer release. ## Rules - Keep `installer/package.json`, `installer/src/core/version.ts` and `CHANGELOG.md` on the same SemVer version. - Run the release checks before tagging. - Tag format: `installer-v<semver>` (for example, `installer-v0.23.0`). - The changelog is updated before the tag. - Never force-push a tag. - Never publish to npm or publish a release from the local machine. ## Canonical sequence ### 1. Prepare the version Update the installer version pointers and changelog, then commit the explicit paths. ```bash git add installer/package.json installer/src/core/version.ts CHANGELOG.md git commit -m "chore(release): prepara installer v<version>" ``` ### 2. Run release checks Run the focused tests and installer typecheck required by the release change. Do not use a local production build as the publication path. ### 3. Tag and push ```bash git tag -a installer-v<semver> -m "installer-v<semver>" git push origin installer-v<semver> ``` ### 4. Verify GitHub assets `.github/workflows/installer-release.yml` builds the four installer binaries, generates `checksums.txt`, and publishes them with `install.sh` as GitHub Release assets. Verify that workflow and its assets after it completes. ```bash gh run list --workflow installer-release.yml --limit 3 gh run watch <run-id> --exit-status ``` ## Troubleshooting - If the workflow fails, inspect it with `gh run view <run-id> --log`.