## What & why

Releases should happen on merge to `main`, driven by the Conventional
Commit messages, like tmp-companion; release-please's release PR (#9,
closed) added a manual step and committed version bumps.

- `release.yml`: semantic-release's GitHub Actions recipe (default
plugins) tags `v<version>` and creates the GitHub release whenever a
`feat:`/`fix:` lands; the Tauri job stamps the version at build time
(`npm version --no-git-tag-version`, never committed) and uploads signed
+ notarized macOS DMGs (Apple Silicon, Intel) and Linux
`.deb`/`.AppImage`.
- Root `package.json`/lockfile: semantic-release back; release-please
config and manifest removed.
- Docs (BUILDING, CONTRIBUTING, CLAUDE.md), Dependabot and CodeRabbit
configs updated.

Merging this cuts the first release (`v1.0.0`, from the `feat:` initial
commit).

Trade-off: semantic-release depends on `@semantic-release/npm`, which
bundles the npm CLI and its own copies of undici, ip-address,
brace-expansion and http-cache-semantics, so those Dependabot alerts
return. They only affect the release tooling (nothing is published to
npm, nothing ships).

## How it was tested

- [x] `scripts/check.sh quick`, `actionlint`, `npm ci`
- [ ] First release run after merge

## Checklist

- [x] Conventional-commit title and commits
- [x] Docs updated

🤖 Generated with [Claude Code](https://claude.com/claude-code)


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Release Process**
* Releases are now created automatically from qualifying commits merged
into the main branch, followed by desktop app builds and uploads.
* The release version is applied during the build without changing the
committed desktop app version.

* **Documentation**
* Updated release and pull-request guidance to reflect the new release
process.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>