Repository navigation
chore: move to iii 0.25.1 - #1694
Conversation
Pin the engine, iii-sdk and @iii-dev/helpers to 0.25.1, refresh the per-platform engine SHA-256 table and carry the pin through the docs.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Caution Review failedThe pull request is closed. No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
Keep the engine at 0.25.1 and take state 0.22.22 and http 0.22.8 from main.
…t the Windows auto-install The Docker build now rejects an engine whose version only contains the pin as a prefix. An AGENTMEMORY_III_VERSION=0.25.0 override still auto-installs. The release-gate receipt names the installed engine pin. The English install docs describe the automatic Windows ZIP install that the CLI already performs.
… on refresh The Docker check compares whole version tokens, so 0.25.1-beta and lookalike strings no longer pass. engine:hashes now replaces only the refreshed version and keeps the other checksum entries.
Summary
Move the engine,
iii-sdkand@iii-dev/helperspins from 0.25.0 to 0.25.1.iii 0.25.1 has one change (iii-hq/iii#2437, native Windows Worker Compose):
cmd /Cwithout MSVC argument escaping, so apath://worker whose run command has quotes no longer fails withERROR_BAD_NETPATH. This is the agentmemory worker on a Windows install path with spaces.CREATE_NO_WINDOWwhen the supervisor has no console, so a start no longer opens empty console windows.Changes
package.json:iii-sdkand@iii-dev/helpersat exactly 0.25.1.src/version.ts:III_PINNED_VERSIONis 0.25.1.src/cli/engine-install.ts: SHA-256 table for the seven 0.25.1 release archives fromnpm run engine:hashes(each archive hash matches the published.sha256asset).npm run docs:synccarried the pin through the docs, deploy files, examples and the console migration link. Historical benchmark receipts, the changelog and the 0.25 upgrade note keep 0.25.0.Worker pins are unchanged.
Test plan
npm run build,npm run docs:check,npm run skills:checknpm run engine:hashes: all seven archive hashes match the published.sha256assets; the darwin-arm64 archive was downloaded again and hashed by hand (f7eff803...0f141), and the binary reports0.25.1npm test(local,--testTimeout=60000): 4458 passed, 6 skipped, 3 failed. The 3 failures aretest/graph-query.test.tstimeouts that also fail on main on the same host (load average above 200 during the run)node scripts/release-gate/startup.mjswith the 0.25.1 engine: 16/17 passed.cancel-external-startupfails the same way on main with 0.25.0 on this host ({"code":null,"signal":"SIGTERM"}), so it is not caused by this changewindows smokeCI job covers itSummary by CodeRabbit