chore: release 0.3.2

Patch release for the npm launcher fix (#41, #42): `idx` and `idx-mcp`
now install their binary on first run when the package manager skipped
postinstall, as npm 12 does under `npx` with its `allow-scripts` policy
(and pnpm 10+ and bun by default).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V3syn2fN2LNo5pvTSqc6eh
This commit is contained in:
hermes 2026-10-16 04:53:56 +00:00
commit c6ec583edc
8 changed files with 13 additions and 13 deletions

View file

@ -38,7 +38,7 @@ npx idx-cli --help
```
The package version and the release tag must match. For example, package
version `0.3.1` downloads assets from the `v0.3.1` GitHub Release.
version `0.3.2` downloads assets from the `v0.3.2` GitHub Release.
The postinstall script downloads `SHA256SUMS` from the same release and
refuses to install a binary whose checksum does not match.
@ -105,7 +105,7 @@ URLs must stay aligned with `scripts/install.js`.
To attach binaries to a tag that already exists, run the workflow manually:
```bash
gh workflow run release.yml -f tag=v0.3.1
gh workflow run release.yml -f tag=v0.3.2
```
Pull requests that touch the workflow or the installer run the build jobs