Repository navigation
chore(release): drop 0.11.2-rc.1 to bare 0.11.2 - #29233
Conversation
First Principles Review (Opus 5.5) — ✅ PASSPremise-level review of First-Principles-Verdict: PASS Nothing to check. What this change shipsInventory (1 items) — 1 justifiedIntent: let maintainers promote the 0.11.2 hotfix to stable by declaring the bare version the stable-gate requires. This is a FIX (release step).
[FIRST-PRINCIPLES-REVIEWED] 8b87028 Description read[DESCRIPTION-READ] 629c49b2f3e4824be4302dc260bb15014e21e09efcfe063d9e7c2e1f88fc32b1 That sha256 names the PR description this verdict read. Recompute it with |
Design Review (Opus 5.5) — ✅ PASSDesign-level review of Design-Verdict: PASS This follows step 1 of the documented RC-to-stable runbook: only the three declared version strings change, and nothing is taken away. [DESIGN-REVIEWED] 8b87028 Description read[DESCRIPTION-READ] 3e9057ffc34a047b211256dc1b765639100a48d06d47dcb597be762b6eb24884 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: |
UX Review (Opus 5.5) — ✅ PASSUX-level review of UX-Verdict: PASS Nothing to check. The diff changes only the version string from [UX-REVIEWED] 8b87028 Description read[DESCRIPTION-READ] 53257e12a5ec43721595c72413e10e9938ebc114ba845f91afdebfcf32b2892e That sha256 names everything this verdict read: the PR description, plus the 3 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 |
Problem / Motivation
Goal: Make
release/0.11.0declare the bare version 0.11.2, so the 0.11.2 hotfix can be promoted to stable.The release branch declares
0.11.2-rc.1in all three version files. Thestable-gatejob refuses a barev0.11.2tag on a commit whose version files do not say0.11.2(docs/build/release.md, "Runbook: promoting an RC to stable", step 1).Why it matters
Without this change, the 0.11.2 hotfix cannot ship to stable. Stable users stay on 0.11.1 without its KAS and MCP fixes.
Not a goal
## [0.11.2] - 2026-11-03already landed with chore(release): start the 0.11.2 hotfix line (0.11.2-rc.1 and its CHANGELOG) #29135, and the code stays the same asv0.11.2-rc.1.packaging/kiro-cli-versionstays at 2.36.0, as in chore(release): drop the rc suffix for the 0.11.1 stable cut #26781.What changed (motivation → approach → change)
Goal: a promotion candidate for 0.11.2 -> approach: step 1 of the documented runbook, the version drop -> change:
0.11.2-rc.1to0.11.2insrc/kiro_crew/__init__.py,pyproject.tomlandwebsite/electron/package.json. This is the same change as the 0.11.1 drop (#26781).Backwards compatibility
Compatible: only the declared version string changes, from a prerelease to the bare release of the same version.
Removes nothing: the diff changes three version strings and removes no path, key, record or function.
Tests
No test added: the existing release gates cover the version files.
test/test_stable_release_gate.py,test/test_changelog_parse.py,test/test_changelog_history_gate.py,test/test_release_promotion_contract.py,test/test_stable_version_display.pyandtest/test_nightly_version_contract.py: 180 passed on this branch.scripts/check_changelog_history.pywithCHANGELOG_BASE_REF=origin/release/0.11.0: OK.Manual verification
grepfor0.11.2-rcin the three version files returns nothing on this branch.Related Issues
N/A: release PRs have no tracking issue. Part of the 0.11.2 hot patch (#28835, #29135).
Checklist
feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)Contribution License Agreement
Contributed under the project's Apache-2.0 license.