Repository navigation
chore: 0.13 backport, bump the bundled KAS engine to 0.66.117 on Node 22.23.4 (#38228, #39211) - #39376
Conversation
… 22.23.4 (#38228, #39211) Backports two main PRs to release/0.13.0, in pick order: - #38228 chore: bump the bundled KAS engine pin to 0.66.117 (cherry picked from commit b490cdf) - #39211 chore: bump the bundled kas node runtime to 22.23.4 (cherry picked from commit 5525caa) Both picks applied without conflicts and without edits. #39211 pins the 0.66.117 engine republished with Node 22.23.4, so it needs #38228 first. Nothing left out.
UX Review (Opus 5.5) — ⏭️ skippedRevision |
First Principles Review (Opus 5.5) — ✅ PASSPremise-level review of First-Principles-Verdict: PASS This is a straight backport of two main PRs. Every item comes either from the measured engine change or from the Goal of matching main, so nothing blocks. Notes
What this change shipsInventory (6 items) — 5 justifiedIntent: 0.13.0 users get the same patched KAS engine and Node runtime as main. This is a FIX (dependency/security bump), backported.
[FIRST-PRINCIPLES-REVIEWED] 81bb3c3 Description read[DESCRIPTION-READ] 82bdd1ddca5c9c80762846eb138d88eaf95b0f5d5d1b709fa6575ec33504bdb9 That sha256 names the PR description this verdict read. Recompute it with |
Design Review (Opus 5.5) — ✅ PASSDesign-level review of Design-Verdict: PASS Nothing blocks: this backports #38228 and #39211 onto the release branch exactly as they landed on main, and the Notes
[DESIGN-REVIEWED] 81bb3c3 Description read[DESCRIPTION-READ] 45fdc3e15a3da681839129af3212dfbfa35ceb89b4d4868a6f6caa24a18d9630 That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with |
Opus 5.5 Review — ✅ no blocking findingsReviewed Verdict parsed from the review's SHA-scoped output markers for commit False positive or not applicable? A repository writer can comment: |
GPT 6.1 Review — ✅ no blocking findingsGPT 6.1 completed its review of This comment is updated in place on each push. Review detailsNo findings. False positive or not applicable? A repository writer can comment: |
Problem / Motivation
Goal: The 0.13.0 release installs the same KAS engine as main: 0.66.117 on Node 22.23.4.
release/0.13.0pins KAS 0.66.104, which ships Node 22.23.3. Main moved to 0.66.117 in #38228 and to the Node 22.23.4 republish of it in #39211. Node 22.23.4 is the 2026-10-21 security release for the 22.x line.Why it matters
The bundled Node is a private runtime users cannot patch themselves: the manifest pins every Node build by sha256. Without this backport, 0.13.0 users keep Node 22.23.3 for a full release cycle.
Not a goal
What changed (motivation → approach → change)
modelselect aftersession/new, so the start path reads it from the notification stream and settles it before the first prompt. Bundle fixtures re-captured on 0.66.117.0.66.117-node22.23.4, the same engine build republished with Node 22.23.4.KAS_PIN_ENGINE_RELEASEstrips the-nodesuffix wherever engine versions are compared.Both are
git cherry-pick -xpicks squashed into one commit, with no conflicts and no edits. #39211 needs #38228 first, because its pin is a republish of 0.66.117. The picks touchacp/kas_pin.py,acp/kas_bundle.py,acp/kas_engine_features.py, theacp/session_handle_*model-select and MCP files,acp/runtime_session_load.py,agent_sdk/kas_model_catalog.py,cli_parser_gateway.py(thekas install --versionhelp text), the bundle fixtures and their tests, and the two specs, same as on main.Backwards compatibility
Compatible: the installer resolves whatever directory the pin names, and
kas/0.66.104/stays published, so older builds keep installing.Removes nothing.
Tests
test/test_kas_pin.py,test/test_kas_model_catalog.py,test/test_kas_model_select_capture.py,test/test_harness_parity.pyand the other updated KAS and session tests), same as chore: bump the bundled KAS engine pin to 0.66.117 #38228 and chore: bump the bundled kas node runtime to 22.23.4 #39211.test_kas_*,test_acp_frame*,test_session_handle*andtest_real_adapter*file: 6317 passed, 33 skipped, 1 failed. The one failure (test_kas_cli_floor.py::TestTheProbeRunsTheSpawnBinary::test_a_timed_out_probe_kills_the_whole_probe_tree,os.pidfd_openmissing) fails the same way on cleanrelease/0.13.0: the local Python build has nopidfd_open.Manual verification
N/A: the full CI matrix on this release branch is the check a backport needs.
Screenshots / video
N/A: no UI change.
Related Issues
Part of #38226
Part of #20727
Backport of #38228 and #39211 to
release/0.13.0.Sibling sweep
Swept: later main commits to
src/kiro_crew/acp/kas_pin.pySibling: none -- #39211 is the latest change to the pin on main
Pattern harvest
Not generalizable: an engine pin backport; both picks apply cleanly.
Checklist
feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)Contribution License Agreement
Contributed under the project's Apache-2.0 license.