Skip to content

chore: move to iii 0.25.1 - #1694

Merged
rohitg00 merged 4 commits into
mainfrom
chore/iii-0.25.1
Nov 7, 2026
Merged

rohitg00 merged 4 commits into
mainfrom
chore/iii-0.25.1

Conversation

@rohitg00

@rohitg00 rohitg00 commented Nov 6, 2026 •

Copy link
Copy Markdown
Owner

Summary

Move the engine, iii-sdk and @iii-dev/helpers pins from 0.25.0 to 0.25.1.

iii 0.25.1 has one change (iii-hq/iii#2437, native Windows Worker Compose):

  • Compose passes shell command text to cmd /C without MSVC argument escaping, so a path:// worker whose run command has quotes no longer fails with ERROR_BAD_NETPATH. This is the agentmemory worker on a Windows install path with spaces.
  • Detached Compose children start with CREATE_NO_WINDOW when the supervisor has no console, so a start no longer opens empty console windows.
  • The engine log is opened read/write before sanitization or rotation, so an existing log no longer fails with access denied.

Changes

  • package.json: iii-sdk and @iii-dev/helpers at exactly 0.25.1.
  • src/version.ts: III_PINNED_VERSION is 0.25.1.
  • src/cli/engine-install.ts: SHA-256 table for the seven 0.25.1 release archives from npm run engine:hashes (each archive hash matches the published .sha256 asset).
  • npm run docs:sync carried 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:check
  • npm run engine:hashes: all seven archive hashes match the published .sha256 assets; the darwin-arm64 archive was downloaded again and hashed by hand (f7eff803...0f141), and the binary reports 0.25.1
  • npm test (local, --testTimeout=60000): 4458 passed, 6 skipped, 3 failed. The 3 failures are test/graph-query.test.ts timeouts that also fail on main on the same host (load average above 200 during the run)
  • node scripts/release-gate/startup.mjs with the 0.25.1 engine: 16/17 passed. cancel-external-startup fails the same way on main with 0.25.0 on this host ({"code":null,"signal":"SIGTERM"}), so it is not caused by this change
  • Native Windows was not run locally; the windows smoke CI job covers it

Summary by CodeRabbit

  • New Features
    • Native Windows setup can automatically download, verify, and extract the pinned iii-engine v0.25.1 release. Manual installation guidance is available if automatic setup fails.
  • Updates
    • Updated the pinned engine and related SDK versions to 0.25.1 across setup instructions, examples, and deployment guidance.
    • Added release checksums for the 0.25.1 engine assets.
  • Bug Fixes
    • Deployment version checks now require an exact version match rather than accepting partial matches.

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.
@vercel

vercel Bot commented Nov 6, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
agentmemory Ready Ready Preview Nov 7, 2026 7:34am UTC

Request Review

@coderabbitai

coderabbitai Bot commented Nov 6, 2026 •

Copy link
Copy Markdown
Contributor

Explain Change →

Caution

Review failed

The pull request is closed.

No actionable comments were generated in the recent review.

Walkthrough

The pinned iii engine and SDK versions change from 0.25.0 to 0.25.1. Source configuration, deployment defaults, release hashes, and installation guidance are updated. Native Windows setup guidance now describes automatic download and extraction, with manual installation as a fallback.

Changes: iii Version Update

Layer / File(s) Summary
Engine and SDK pins
src/version.ts, package.json, examples/python/*, src/cli.ts, eval/README.md, scripts/docs-sync.state.json, scripts/release-gate/run.mjs, website/app/security/page.tsx, AGENTS.md, .env.example
The pinned version and related references change to 0.25.1.
Engine installation and validation
src/cli/engine-install.ts, scripts/engine-hashes.mjs, test/engine-install.test.ts, deploy/Dockerfile
The installer adds SHA-256 values for the 0.25.1 release assets. The hash-generation script retains other version entries. The regression test checks 0.25.0 checksums, and the Docker version check requires an exact token match.
Deployment engine pin
docker-compose.yml, deploy/runtime/entrypoint.sh, deploy/README.md, deploy/fly/README.md, deploy/railway/README.md, deploy/render/README.md
The Docker and Compose version defaults change to 0.25.1. Deployment documentation and the runtime ownership comment identify the same version.
Installation guidance
INSTALL_FOR_AGENTS.md, README.md, READMEs/README.*.md
The agent runbook and main README describe automatic native Windows download and extraction, with manual installation as a fallback. The localized README instructions update the pinned version and release links; they continue to describe manual installation.

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Other

Possibly related PRs

Suggested reviewers: guibeira

Merge Risk: Low · up to df422

After merge, the runbook may expect a newer engine than the published package installs. Coordinate the documentation and package release.

Pre-merge checks: Passed 5

Check name Status Explanation
Description Check Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check Passed The title clearly identifies the upgrade to iii 0.25.1, the main change in the pull request.
Docstring Coverage Passed No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage

Explanation

No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 9 files. (4 skipped: 4 unsupported.)

  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

Recent review info

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: d080212e-a39d-4fd0-b552-0eaafbf1f79c
Commits

Reviewing files that changed from the base of the PR and between 54492a3 and 5e231b7.

Files selected for processing: 7

  • .env.example
  • INSTALL_FOR_AGENTS.md
  • README.md
  • deploy/Dockerfile
  • scripts/release-gate/run.mjs
  • src/cli/engine-install.ts
  • test/engine-install.test.ts
Files skipped from review as they are similar to previous changes: 1

  • .env.example

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 7 remain after this review.

devin-ai-integration[bot]

This comment was marked as resolved.

Keep the engine at 0.25.1 and take state 0.22.22 and http 0.22.8 from main.
coderabbitai[bot]

This comment was marked as resolved.

…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.
devin-ai-integration[bot]

This comment was marked as resolved.

… 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.

This branch was successfully deployed

1 active deployment
Preview — df4225a9 Deployed Nov 7, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant