Skip to content

chore(release): 0.13.1 (version and CHANGELOG) - #40206

Merged
bolichen97 merged 1 commit into
release/0.13.0from
release-prep/0.13.1
Nov 21, 2026
Merged

bolichen97 merged 1 commit into
release/0.13.0from
release-prep/0.13.1

Conversation

@bolichen97

Copy link
Copy Markdown
Contributor

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.0 have no version or release notes yet. The three version files still say 0.13.0 and CHANGELOG.md has no ## [0.13.1] section.

Why it matters

The stable v0.13.1 is cut from the RC commit that soaked on insider. That commit has to declare 0.13.1 in 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

  • No code change: every fix in the section already merged through its own backport PR.
  • No edit to any shipped CHANGELOG section.
  • No website/electron/package-lock.json change, as in the 0.12.2 version commit.

What changed (motivation → approach → change)

src/kiro_crew/__init__.py, pyproject.toml and website/electron/package.json move from 0.13.0 to 0.13.1, and CHANGELOG.md gains a ## [0.13.1] - 2026-11-20 section above ## [0.13.0]. This is the same shape as the 0.12.2 version commit 3d06d4604b on 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, under docs/build/changelog.md: an opening paragraph and a ### Notable fixes section 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.1 on the merge commit as the gate build, so the bare v0.13.1 can name the same commit after the soak.

Backport PRs covered by the section:

  • #39476 browser engine reinstall after an update
  • #39539 queue hand-off behind a turn cancelled before it starts
  • #39602 Fresh start past a held message, held queue cards, idle pane re-reads
  • #39641 a bundle beside a deny no longer holds every Bot call
  • #39571 split pane files open in the side panel
  • #39730 no empty Bot row in the Sessions list
  • #39734 drop the ask rules an every-call hold wrote into a Bot file
  • #39762 project AWS profile read answers in time
  • #39768 confirm before conductor mode locks a chat
  • #39767 stop an unattended build when the user says later
  • #39912 MCP sign-in for an OAuth 401 with no challenge
  • #39904 cloud launch zone retry, cancel, and HTTPS tag pin
  • #39598 MCP gateway initialize deadline and its reap memory
  • #40102 KAS boot engine check asks again
  • #40002 App Store listing answers within 5 s
  • #39859 two false exfil refusals

Backwards compatibility

Compatible: only the declared version and a new CHANGELOG section change. The two manifests change only their version field, 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.0 as the base:

  • 61 of 62 gates exit 0. That includes isort, flake8, mypy, black, docs lint, gen:ui -- --check, tsc, eslint, i18n, the scoped frontend tests (15753 passed) and test:electron (3909 passed). check_changelog_history.py says the 20 shipped sections at the base are intact.
  • The scoped backend tests ran 20505 passed and 56 failed. All 56 fail the same way on a clean origin/release/0.13.0 checkout 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 (unshare EPERM). CI is the authority for these.
  • The changelog and version test files (test/test_changelog*.py, test/test_*version*.py, test/test_feed_release_notes.py): 577 passed.
  • The section has no em or en dashes, checked by a byte scan.

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

  • At most two commits (one is the norm), with a Conventional Commits title
  • Existing tests pass and new tests added for new functionality
  • Self-review completed; code follows project style guidelines
  • Documentation updated (if applicable)
  • No secrets, credentials, or internal references in the diff

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.
@bolichen97
bolichen97 requested review from a team and KiroCrewCaptain as code owners November 20, 2026 23:19
@bolichen97
bolichen97 requested review from mbriones98 and removed request for a team November 20, 2026 23:19
@github-actions

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5) — ✅ PASS

UX-level review of dc2717aa5dd985826996f01ce1063756d0e2a8a4 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

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 .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ PASS

Design-level review of dc2717aa5dd985826996f01ce1063756d0e2a8a4 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

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 .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

Reviewed dc2717aa5dd985826996f01ce1063756d0e2a8a4 — this comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] dc2717a

Verdict parsed from the review's SHA-scoped output markers for commit dc2717aa5dd985826996f01ce1063756d0e2a8a4.

False positive or not applicable? A repository writer can comment:
/ai-review override fable dc2717aa5dd985826996f01ce1063756d0e2a8a4 false-positive: <reason, 20 to 500 characters>

@github-actions

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — ✅ PASS

Premise-level review of dc2717aa5dd985826996f01ce1063756d0e2a8a4 — why this exists and whether the shipped surface is the smallest honest version. Updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

First-Principles-Verdict: PASS

Nothing to check.

What this change ships

Inventory (5 items) — 5 justified

Intent: 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).

  1. The Python package now reports version 0.13.1 (pyproject.toml) — justified
  2. The __version__ string the runtime reports is now 0.13.1 — justified
  3. The Electron desktop app reports version 0.13.1 — justified
  4. A new ## [0.13.1] - 2026-11-20 CHANGELOG section sits above 0.13.0, with no edits to earlier sections — justified
  5. The Releases page will render notes for the 16 hotfix PRs listed in the description — justified

[FIRST-PRINCIPLES-REVIEWED] dc2717a

Description read

[DESCRIPTION-READ] 3983b30a348ac40a60d9baec1c22949f017cee007a2dfcb1dd51bfa1678c42d2

That sha256 names the PR description this verdict read. Recompute it with .github/scripts/pr-description-capture.sh; if it differs, the description changed after this verdict was formed and any finding drawn from the description is unproven.

@github-actions

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings

GPT 6.1 completed its review of dc2717aa5dd985826996f01ce1063756d0e2a8a4 and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] dc2717a

False positive or not applicable? A repository writer can comment:
/ai-review override gpt dc2717aa5dd985826996f01ce1063756d0e2a8a4 false-positive: <reason, 20 to 500 characters>

@bolichen97
bolichen97 merged commit 10cf312 into release/0.13.0 Nov 21, 2026
91 of 93 checks passed
@bolichen97
bolichen97 deleted the release-prep/0.13.1 branch November 21, 2026 00:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant