Skip to content

intent-cli v0.32.0

Choose a tag to compare

@tomohisa tomohisa released this 22 Sep 19:55
7fa4e50

v0.32.0 release at the G850 merge 7fa4e500323771a71365c8a0ac74eab269d103cf.

Measured at that commit: v0.31.0..7fa4e500 is 51 first-parent commits, classified as 42 shipped units, 4 release-preparation commits and 5 claim or state commits. Nine units landed after v0.32.0-preview.4 (ba496314): G839, G840, G841, G847, G846, G845, G842, G849 and G848.

What a preview.4 user acts on:

  • Cross-runtime review gains two runtimes (G842). GitHub Copilot CLI and OpenCode join codex, claude and cursor for review cross-runtime request|record|status, as a declared conductor_runtime, and as builders in guide solo-conductor. --model is required for copilot and opencode on both kinds; --effort and the request-only --opencode-provider-config are theirs too. intent-cli renders the pinned invocation text and records the verdict; it never launches a reviewer, a builder or a provider.
  • Issue bodies are checked before they are sent (G845, G846, G847). The four gh --body-file routes and the three gh api --input JSON-payload routes refuse a malformed or oversized body, and issue validate-body, packet draft and issue publish-flow report the size before any GitHub write, with a warning band. 65,536 bytes and 58,000 bytes are intent-cli's own conservative limit and warning band; GitHub's actual boundary was not verified.
  • Two follow-ups from the G842 review (G848, G849). On non-Windows, request refuses an --opencode-provider-config source that group or other can access, and reads it once through one checked handle. The copilot reviewer invocation pins GH_CONFIG_DIR, so a gh token kept in hosts.yml still authenticates under the isolated XDG_CONFIG_HOME.
  • Refusals name their cause (G839, G841), and two flaky CLI tests are deterministic (G840).

Full notes: docs/en/release-notes-v0.32.0.md and docs/ja/release-notes-v0.32.0.md.

Release assets and packages are produced by the release workflow.