chore: release 0.3.1

Patch release for the fixes from the Codex review of 0.3.0: ticker
validation and encoded cache file names (path traversal via a ticker),
cross-process ownership DB locking, history-preserving snapshot sync,
and MCP input limits. MSRV is now 1.89.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
hermes 2026-10-15 03:14:45 +00:00
commit aac30335fc
7 changed files with 12 additions and 12 deletions

View file

@ -11,7 +11,7 @@ Each release also carries a copy of the script as a release asset, so a
versioned URL stays stable:
```bash
curl -fsSL https://github.com/0xrsydn/idx-cli/releases/download/v0.3.0/install.sh | sh
curl -fsSL https://github.com/0xrsydn/idx-cli/releases/download/v0.3.1/install.sh | sh
```
## What it does
@ -45,7 +45,7 @@ them yourself.
Pass flags through the pipe with `sh -s --`:
```bash
curl -fsSL https://raw.githubusercontent.com/0xrsydn/idx-cli/main/install.sh | sh -s -- --version v0.3.0 --dir ~/bin
curl -fsSL https://raw.githubusercontent.com/0xrsydn/idx-cli/main/install.sh | sh -s -- --version v0.3.1 --dir ~/bin
```
## Supported platforms

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.0` downloads assets from the `v0.3.0` GitHub Release.
version `0.3.1` downloads assets from the `v0.3.1` GitHub Release.
The postinstall script downloads `SHA256SUMS` from the same release and
refuses to install a binary whose checksum does not match.
@ -88,7 +88,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.0
gh workflow run release.yml -f tag=v0.3.1
```
Pull requests that touch the workflow or the installer run the build jobs