Repository navigation
chore(release): forward-port the 0.11.2 fixes to release/0.12.0 - #29148
Conversation
Every main PR the 0.11.2 backport carried that release/0.12.0 still lacks, plus #28925, cherry-picked with -x in main merge order, oldest first, then squashed (PR Hygiene allows two commits). Each pick's added and removed lines match its main commit except where noted. - fix(mcp): refuse to replace an unparseable global mcp.json (#28023) (cherry picked from commit 52184dd) conflict in surrounding lines only; the changed lines are main's. - fix(kas): read allowedCommands classes, groups and quoted parens like kiro-cli (#28437) (cherry picked from commit 3fc4217) conflict in surrounding lines only; the changed lines are main's. - feat(dashboard): answer /context, /usage, /help and /agent locally on KAS (#26681) (cherry picked from commit 84ea89d) - fix(mcp): skip a non-UTF-8 mcp.json in discovery like bad JSON (#28795) (cherry picked from commit 2af230d) - fix(kas): split an authored rule's long match instead of refusing the block (#28510) (cherry picked from commit 60595c7) - fix(kas): carry session identity to builtin app MCP servers (#28732) (cherry picked from commit 8e9701f) - fix(kas): relay a remote MCP server's headers through a local bridge (#28615) (cherry picked from commit 755c71b) - fix(kas): mount use_subagent as the engine's invoke_sub_agent (#28852) (cherry picked from commit 83a76fc) - feat(kas): keep remote MCP sign-ins across sessions by default (#28630) (cherry picked from commit 00dc406) conflict in surrounding lines only: docs/decisions/README.md and configuration.md lack neighbouring rows 0.12.0 does not carry. - fix(project-dir): treat an EPERM marker probe as absent so MCP start-up survives a masked mount (#28595) (cherry picked from commit 742ae56) - fix(kas): judge a remote-wrapper web search as its built-in (#28704) (cherry picked from commit 54f4e14) - fix(acp): remove a new KAS session's app launch snapshots at shutdown (#28954) (cherry picked from commit 1217a85) - fix: run spec hook commands longer than 4096 characters on kas (#28925) (cherry picked from commit 0fe72d6) adapted: agent-host-contract.md gets main's inserted sentence in 0.12.0's paragraph, which lacks main's later user-hook-files text.
Sensitive Change ReviewSensitive files changed:
How to clear this check:
Only the author's comment counts this way. A reviewer can instead |
UX Review (Opus 5.5) — ⏭️ skippedRevision |
Design Review (Opus 5.5) — ✅ PASSDesign-level review of Design-Verdict: PASS Nothing blocks: each pick forward-ports a fix already merged on Notes
[DESIGN-REVIEWED] c33250d Description read[DESCRIPTION-READ] 3119b7556a040cbed0c09427422383efa99d5e3286815c162f9259cc3f593f3a 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 |
First Principles Review (Opus 5.5) — 🔴 BLOCKPremise-level review of First-Principles-Verdict: BLOCK Item 9 changes a default that nearly everyone gets. What this change shipsInventory (10 items) — 9 justifiedIntent: give 0.12 insiders every fix that 0.11.2 already shipped, so nothing regresses when they upgrade. This is a FIX (a forward-port).
Blockersproduct-shape change without accepted RFC: KAS keeps remote MCP sign-ins by default — rides along [FIRST-PRINCIPLES-REVIEWED] c33250d Description read[DESCRIPTION-READ] c16d2e16840cb84e1f208f6e15b9bf1d8ad51d87fd8893b49bdc62d26c99ecf2 That sha256 names the PR description this verdict read. Recompute it with |
Declare 0.12.0-rc.6 in all three version files so the next insider RC ships the 0.11.2 fixes forward-ported by #29148.
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: |
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: |
Security Scope Review -- ✅ PASSWhich legitimate operations does Verdict basis: adjudicated, zero confirmed regressions. Security scope review -- adjudicated candidates
No candidate flipped from allowed to refused. Scope-Verdict: PASS Reason: Nothing in this diff makes the shell deny composite ( TIGHTENING: ADJUDICATED: 16 candidates, 0 confirmed newly-refused PLATFORM COVERAGE: posix and windows. The diff assumes one thing about platforms: UNADJUDICATED:
[SCOPE-REVIEWED] c33250d |
Problem / Motivation
Goal: Bring every fix the 0.11.2 hotfix carries, and that
release/0.12.0still lacks, ontorelease/0.12.0sov0.12.0-rc.6ships them and no 0.11.2 fix regresses when an insider moves to 0.12.release/0.12.0was cut before these main PRs merged. The 0.11.2 backport (#28835) put them onrelease/0.11.0, so without this PR an insider on 0.12.0-rc.6 would lack fixes a 0.11.2 user has. #28925 merged on main after #28835 and is included so the two lines stay level.Why it matters
The KAS and MCP failures these PRs fix (spec hooks that silently do nothing, an unparseable
mcp.jsonreplaced, remote MCP sign-ins asked for again in every session, MCP start-up dying on a masked mount, app MCP servers without session identity) would hit every insider on the 0.12 line. A user who upgrades from 0.11.2 to 0.12.0-rc.6 would see them come back.Not a goal
main; nothing is changed only here.0.12.0-rc.6is its own PR after this one merges (the chore(release): 0.12.0-rc.5 #28430 shape).CHANGELOG.mdchange.release/0.12.0already carries (fix(hooks): give KAS-run agent spec hooks KIRO_SESSION_ID #24952, fix(acp): send a KAS session the kiro-cli spelling of a stored model id #25671, fix(kas): start Crew's own MCP servers first so session start does not wait behind slow user servers #26148, fix(acp): offer a KAS MCP sign-in only when the user names the server #26481, fix(kas): start env-bearing MCP servers through a local launcher #26785, fix(kas): refuse a blank kas remove --version instead of deleting every engine #26623, feat(dashboard): answer /model, /tools and /mcp locally on KAS #26471, fix(mcp): heal a saved absolute Windows command's PATHEXT extension #25945, fix(dashboard): give every MCP handler error a stable code #26661).What changed (motivation → approach → change)
Each main PR was cherry-picked with
-xontoorigin/release/0.12.0@44ce6619c8(v0.12.0-rc.5), in main merge order, oldest first, then squashed into one commit (PR Hygiene allows two). The commit message lists every source commit.52184dd5483fc421793884ea89db7c2af230df9260595c7f198e9701f109755c71b3c783a76fca1a00dc406099742ae5659354f4e142821217a85d5f0fe72d6165For every pick except #28925, the added and removed lines match its main commit line for line. The conflicts were all in neighbouring lines that
release/0.12.0has a different version of:docs/decisions/README.mdandconfiguration.mdlack neighbouring rows that 0.12.0 does not carry. Only this PR's decision row and itsagent.kas_persist_mcp_sign_inrow were taken. 0.12.0'sagent.kas_bundlerow is kept as is.agent-host-contract.md's spec-hooks paragraph on 0.12.0 lacks main's later user-hook-files sentences. Main's inserted sentence is placed at the same spot, word for word.security.paths.MAX_SCANNABLE_COMMAND_CHARS, which the code change uses, exists on 0.12.0.Backwards compatibility
Compatible: each change is the one already merged on
mainand onrelease/0.11.0(except #28925, which is onmainonly). Each PR's own compatibility note applies unchanged.Removes nothing: no pick hides, deletes or renames anything 0.12.0 accepts. #28630 changes the
agent.kas_persist_mcp_sign_indefault, recorded indocs/decisions/2026-11-02-kas-keeps-remote-mcp-sign-ins-by-default.md(shipped by #28630).Tests
Proof: not provable -- other: a forward-port of main commits whose proofs ran on their own PRs
test/test_acp_copilot_backend.pyfails 3 tests on this host, and the same 3 fail on cleanorigin/release/0.12.0, so they come from the host and not from this diff.mypy src/kiro_crew,check_file_line_cap,check_harness_parity,check_comment_history,check_brand_name,check_subprocess_encoding,check_sync_io_in_asyncanddocs-lintall pass.check_black_formatting.pycould not run here because the local Black is 26.3.1 and the script needs 26.10.1. CI runs it.Manual verification
N/A - every pick was verified on its own main PR. The rc.6 insider build is the end-to-end check.
Related Issues
Forward-port of the 0.11.2 hot patch (#28835) to the 0.12 line, ahead of
v0.12.0-rc.6.Checklist
feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)Contribution License Agreement
Contributions are accepted under the project's Apache-2.0 license; see the Licensing section of CONTRIBUTING.md.