Repository navigation
chore(release): 0.13.1 (version and CHANGELOG) - #40206
Conversation
Move the three version files to the bare 0.13.1 and add the [0.13.1] CHANGELOG section for the hotfix backports merged on release/0.13.0 since v0.13.0, written from git log v0.13.0..release/0.13.0. The gate build v0.13.1-rc.1 is tagged on this commit, as for 0.12.2-rc.1, so the bare v0.13.1 can name it. website/electron/package-lock.json stays as it is.
UX Review (Opus 5.5) — ✅ PASSUX-level review of UX-Verdict: PASS Nothing to check. The diff only bumps the version in three files and adds a CHANGELOG section. It adds or changes no user-visible control, so no screenshot was needed. [UX-REVIEWED] dc2717a Description read[DESCRIPTION-READ] 6df82743205dffafd40c68ce8d83f7c4d37a87b6f07f89341d5a31fdbd843617 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 |
Design Review (Opus 5.5) — ✅ PASSDesign-level review of Design-Verdict: PASS Nothing blocks: a standard release-version commit with the same shape as the 0.12.2 one. It touches no code or rendered surface and removes nothing. [DESIGN-REVIEWED] dc2717a Description read[DESCRIPTION-READ] b3283e7dd858c4b03cdd4e36b78b0a44e4f8f2b830408b0b0d17e21416efa0e2 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: |
First Principles Review (Opus 5.5) — ✅ PASSPremise-level review of First-Principles-Verdict: PASS Nothing to check. What this change shipsInventory (5 items) — 5 justifiedIntent: give the hotfixes already merged on release/0.13.0 their own 0.13.1 version number and release notes, so the next RC can become the stable 0.13.1. This is an ADDITION (a release step).
[FIRST-PRINCIPLES-REVIEWED] dc2717a Description read[DESCRIPTION-READ] 3983b30a348ac40a60d9baec1c22949f017cee007a2dfcb1dd51bfa1678c42d2 That sha256 names the PR description this verdict read. Recompute it with |
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: release/0.13.0 declares the bare 0.13.1 and carries its CHANGELOG section, so the next RC is the 0.13.1 gate build.
The hotfix backports merged on release/0.13.0 since
v0.13.0have no version or release notes yet. The three version files still say0.13.0andCHANGELOG.mdhas no## [0.13.1]section.Why it matters
The stable
v0.13.1is cut from the RC commit that soaked on insider. That commit has to declare0.13.1in all three version files and carry the section the Releases page renders, or 0.13.1 ships under the 0.13.0 number with no notes.Not a goal
website/electron/package-lock.jsonchange, as in the 0.12.2 version commit.What changed (motivation → approach → change)
src/kiro_crew/__init__.py,pyproject.tomlandwebsite/electron/package.jsonmove from0.13.0to0.13.1, andCHANGELOG.mdgains a## [0.13.1] - 2026-11-20section above## [0.13.0]. This is the same shape as the 0.12.2 version commit3d06d4604bon release/0.12.0.The section is written from
git log v0.13.0..origin/release/0.13.0(25 commits, all hotfix picks) and the source PRs, underdocs/build/changelog.md: an opening paragraph and a### Notable fixessection grouped by area, at most three sentences per paragraph, each fix named where it lives in the product.After this merges, a person tags
v0.13.1-rc.1on the merge commit as the gate build, so the barev0.13.1can name the same commit after the soak.Backport PRs covered by the section:
Backwards compatibility
Compatible: only the declared version and a new CHANGELOG section change. The two manifests change only their
versionfield, with no dependency added or removed, and every earlier CHANGELOG section is byte-identical.Removes nothing: no code path, key or section is removed.
Tests
On this head, with the profile's 62 gates run against
origin/release/0.13.0as the base:gen:ui -- --check, tsc, eslint, i18n, the scoped frontend tests (15753 passed) andtest:electron(3909 passed).check_changelog_history.pysays the 20 shipped sections at the base are intact.origin/release/0.13.0checkout on the same host, so the failures come from the host. 52 of them pass once the host's temp dir, home and agent environment are kept out. The other 4 need Linux user namespaces, which this host's sandbox refuses (unshareEPERM). CI is the authority for these.test/test_changelog*.py,test/test_*version*.py,test/test_feed_release_notes.py): 577 passed.Proof: not provable -- docs or config only
Manual verification
N/A: a version string change and release notes; each fix was verified in its own PR.
Related Issues
Release step for 0.13.1; no tracking issue. A maintainer applies
issue-gate: waived, as for a release PR.Checklist