fix: improve iii runtime compatibility diagnostics#1034
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
0.11.2; iii0.18.0remains explicit opt-in viaAGENTMEMORY_III_VERSION.iii --versionfrom stdout and stderr, while accepting a binary as compatible only when the probe succeeds and the version matches the configured pin.Fixes #337.
Validation
corepack pnpm exec vitest run test/iii-runtime.test.ts test/build-runtime.test.ts test/cli-doctor-fixes.test.ts test/engine-launch.test.tscorepack pnpm run lintcorepack pnpm testcorepack pnpm run buildsemgrep scan --config p/default --error --metrics=off .gitleaks protect --staged --redactgitleaks dir . --redactOSV was not required because this change does not touch dependencies, lockfiles, container files, vendored code, package-manager config, or third-party package surfaces.