Repository navigation
chore(release): bump release/0.12.0 to 0.12.0-rc.6 - #29151
Conversation
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.
Design Review (Opus 5.5) — ✅ PASSDesign-level review of Design-Verdict: PASS Nothing to check. This PR only changes the version string in three files, and all three now say the same RC version. [DESIGN-REVIEWED] c995195 Description read[DESCRIPTION-READ] 511362dac10bc8572521acc1c09601a10e715afe17b77dd5809a7334fcd3f0c8 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 |
UX Review (Opus 5.5) — ✅ PASSUX-level review of UX-Verdict: PASS Nothing to check. The diff only changes the version string in three files, so there is no user-visible control or state to review and no screenshot is needed. [UX-REVIEWED] c995195 Description read[DESCRIPTION-READ] 1967b5dc74e71a3ec7b9ffd205c3ff1af8a648a456205dd18d8a39ed030b78c5 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 |
First Principles Review (Opus 5.5) — ✅ PASSPremise-level review of First-Principles-Verdict: PASS Nothing to check. What this change shipsInventory (3 items) — 3 justifiedIntent: let insider users get the 0.11.2 fixes forward-ported in #29148 by declaring the next RC,
[FIRST-PRINCIPLES-REVIEWED] c995195 Description read[DESCRIPTION-READ] 15b4f870973c2e97ce956bd7e4adb073adf9af1cfe0b8dc6efb2544be8954d70 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: |
Problem / Motivation
Goal: Declare
0.12.0-rc.6onrelease/0.12.0, so the next insider RC ships the 0.11.2 fixes forward-ported by #29148.Why it matters
Insider users only get #29148 from a new RC tag.
v0.12.0-rc.5does not have it.Not a goal
v0.12.0-rc.6after this merges.What changed (motivation → approach → change)
All three version files (
pyproject.toml,src/kiro_crew/__init__.py,website/electron/package.json) declare0.12.0-rc.6, as release.md "Version numbering policy" asks. Same shape as #28430.Backwards compatibility
Compatible: version only.
Removes nothing: only version strings change.
Tests
None needed: version strings only.
Proof: not provable -- version only, no behavior change
Manual verification
Read all three version files on this commit: each says
0.12.0-rc.6, and no0.12.0-rc.5is left in them.Related Issues
Follows #29148.
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.