Repository navigation
v0.3.2
Chat Harness v0.3.2
This patch release fixes npm-managed update checks on npm 12.
Fixed
Chat Harness v0.3.1 queried npm with:
npm view chat-harness@latest version --jsonnpm 12 returns a one-element JSON array for this scalar field, for example:
[
"0.3.1"
]v0.3.1 expected a JSON string and incorrectly reported:
lifecycle.update_failed npm returned an invalid latest version
v0.3.2 now queries the single version field using npm's plain scalar output and validates that value directly.
Scope
This is a narrow compatibility fix.
It does not change:
- installation provenance detection;
- standalone update behavior or SHA-256 verification;
- npm update mutation behavior;
- uninstall behavior;
- Windows lifecycle handling;
- Workspace setup, validation, migration, or data-safety boundaries.
Upgrade
If you are on v0.3.1 with an npm-managed installation, upgrade once with:
npm install -g chat-harness@latest
chat-harness --versionAfter v0.3.2 is installed, the normal lifecycle commands work again:
chat-harness update --check
chat-harness update