Repository navigation
chore(release): backport the last 0.11.1 hotfix fixes to release/0.11.0 - #26627
Conversation
Backports these main fixes to release/0.11.0 after #26487 and #26594: - fix(kas): let a relative file:// prompt use .. like kiro-cli (#26382) (cherry picked from commit 36c95db) - part of #24709 (cherry picked from commit d86c94a, partial): the sandbox_launch_mark module, its note() call in cli.main before the KIROCREW_SANDBOX_ACTIVE pop, and its per-test reset fixture. Nothing else of #24709 (its enterprise policy-cache tier) is included; the module docstring and the cli.py comment name the 0.11.0 reader. - fix(cloud): treat every agent process as an agent in the human-action guard (#26144) (cherry picked from commit dd0dd62) Conflict resolved by hand: - #26382: keeps 0.11.0's acp-client.md (the paragraph it edits is not on 0.11.0); agent-spec-fields.md takes its path-fence bullets and keeps 0.11.0's blank-prompt fallback bullet. Test-only fixes: - test_cloud_aws pins sandbox_launch_mark.SANDBOX_MARKER to sandbox_tiers._IN_SANDBOX_MARKER (the #24709 test that pinned it on main is not on 0.11.0). - test_prompt_override_encoding pins browser_cli.install.available() off: the context build probed the host's PATH for playwright-cli and counted its refusal warning as a second override warning. Left out: #26471 is a feature built on KAS code only main has.
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: this PR copies two [DESIGN-REVIEWED] afdded4 Description read[DESCRIPTION-READ] e041322fea0f8e54c3483720de40a5881e07c111772541953be0293b2bdc2d2c 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) — ✅ PASSPremise-level review of First-Principles-Verdict: PASS This backports fixes already merged on main. Each item has a named harm, and the one deleted pin (the What this change shipsInventory (9 items) — 6 justifiedIntent: give 0.11.0 users the 0.11.1 hotfix fixes (KAS
[FIRST-PRINCIPLES-REVIEWED] afdded4 Description read[DESCRIPTION-READ] 497e07cb533d69e97b86f6e941a7668009353dced190733b87425670db572769 That sha256 names the PR description this verdict read. 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: |
…NGELOG) (#26648) Declare release/0.11.0 as the 0.11.1 hotfix line in the dual-valid RC spelling the version numbering policy requires: all three version files move from 0.11.0 to 0.11.1-rc.1. Add the ## [0.11.1] - 2026-10-31 section, written from the three hotfix backports already on the branch (#26487, #26594, #26627). Every earlier section is unchanged. Co-authored-by: w <w@k.local>
Problem / Motivation
Goal: Ship the last two 0.11.1 hotfix fixes from
mainto the 0.11.0 release line, after #26487 and #26594.0.11.0 still refuses a relative
file://prompt with..on KAS, and its cloud human-action guard recognises only one kind of agent process.Why it matters
The release line is what users install. #26144 is a P0 fix (#26133); without this PR it reaches users only with 0.12.0. On 0.11.0 today, a process run with
KIROCREW_RUNTIME_AGENT=1and noKIROCREW_SESSION_KEYpassescloud.aws.assert_human_action(checked on this branch's base).Not a goal
What changed (motivation → approach → change)
One commit; its message lists every pick and its source sha.
file://prompt check (acp/kas_prompt_paths.py,acp/kas_agents.py,acp/harness/kas.py)cloud/aws.py,dashboard/handlers_cloud.py)sandbox_launch_mark.py, itsnote()call incli.pyand its test reset; #26144 imports itmainhas (ACP_BACKENDS_LOCAL_HARNESS_COMMANDS,switch_slot_model, the KAS bundle route)#26382 keeps 0.11.0's
acp-client.mdand takes its path-fence bullets insrc/kiro_crew/docs/agent-spec-fields.md. The #24709 piece is adapted only in words: the module docstring and thecli.pycomment name the 0.11.0 reader, the cloud guard.test/conftest.pyandtest/conftest_resets.pygain #24709's reset fixture, so a test that sets the marker cannot leak it to later tests;test/conftest.pyalso hides the runner's own markers, as #26144 does onmain. Two test-only fixes:test/test_cloud_aws.pypinsSANDBOX_MARKERto the sandbox's own marker name, andtest/test_prompt_override_encoding.pypins the browser CLI probe off, because the host's playwright-cli on PATH added a warning its counts read as a second override warning.Backwards compatibility
Compatible: each change is its main PR's own. The cloud guard only adds refusals for processes Kiro Crew spawned for an agent; a human terminal and the dashboard's
/api/cloud/*carry none of the markers.Removes nothing: no API, key, row or path is removed.
Tests
The picked tests are the main PRs' own. Run on this head:
test_cloud_aws.py,test_kas_prompt_paths.py,test_kas_agents.py,test_kas_project_agents.py,test_prompt_override_encoding.py) withtest_spawn_audit.py, everytest_cloud*andtest_kas_*file andtest_cli.py: 4082 passed.cloud.aws,assert_human_actionorhandlers_cloud, plus the CLI and sandbox facade tests: 5953 passed.mypy src/kiro_crew/, semgrep (repo rules, diff-scoped), black gate, docs-lint, comment history, flake-pattern ratchet: all pass.test_cloud_aws.Determinism: the tests are the main PRs' own, unchanged; their repeat and shuffled-order runs are recorded on each main PR.
Manual verification
N/A - every change was verified on its own main PR; this PR moves them to the release branch.
Screenshots / video
Why no screenshot: backend-only change with no visible output.
Related Issues
Part of #26133
Backport of #26382, #26144 and part of #24709. Follow-up to #26487 and #26594.
Checklist
feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)Contribution License Agreement
Contributed under the project's Apache-2.0 license.