Skip to content

chore(release): start the 0.11.2 hotfix line (0.11.2-rc.1 and its CHANGELOG) - #29135

Merged
buluoray merged 1 commit into
release/0.11.0from
crew/slack/release-0.11.2-rc1
Nov 3, 2026
Merged

buluoray merged 1 commit into
release/0.11.0from
crew/slack/release-0.11.2-rc1

Conversation

@buluoray

@buluoray buluoray commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: Start the 0.11.2 hotfix line on release/0.11.0: version 0.11.2-rc.1 and the ## [0.11.2] CHANGELOG section, so a maintainer can tag v0.11.2-rc.1.

The 0.11.2 hotfix backports (#28835) are merged on release/0.11.0, but the branch still declares 0.11.1 and has no section for them.

Why it matters

A hot patch needs at least one recorded RC before the bare tag (docs/build/release.md, "Hot patches follow the same rule"). Without this PR the hotfix cannot be tagged, and users on 0.11.1 who are waiting on these KAS and MCP fixes get them only with the next minor.

Not a goal

  • No code change and no new fix.
  • No tag, no merge, no version drop to the bare 0.11.2 (that is a later PR).
  • No change to main; the 0.11.2 section is ported to main when 0.11.2 reaches stable.

What changed (motivation → approach → change)

Same shape as #26648, the 0.11.1 rc.1 PR.

  • All three version files move from 0.11.1 to 0.11.2-rc.1: src/kiro_crew/__init__.py, pyproject.toml, website/electron/package.json.
  • CHANGELOG.md gains ## [0.11.2] - 2026-11-03, written from the fixes chore(release): backport the 0.11.2 hotfix fixes to release/0.11.0 #28835 brought to the branch, as one opening paragraph and a ### Notable fixes tail grouped by area. Every earlier section is unchanged.

Backwards compatibility

Compatible: a version string and one new CHANGELOG section; no contract changes.

Removes nothing: the diff only adds a section and edits a version string.

Tests

Proof: not provable -- docs or config only

  • scripts/check_changelog_history.py against origin/release/0.11.0: every shipped section intact.
  • The changelog and version tests (test/*changelog*, test/*version*): 345 passed.

Manual verification

N/A - a version string and a CHANGELOG section; the RC build is the verification.

Related Issues

Part of the 0.11.2 hot patch (#28835).

Checklist

  • At most two commits (one is the norm), with a Conventional Commits title (feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)
  • 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

Contribution License Agreement

Contributions are accepted under the project's Apache-2.0 license; see the Licensing section of CONTRIBUTING.md.

…NGELOG)

Move the three version files to 0.11.2-rc.1 and add the [0.11.2]
CHANGELOG section for the hotfix backports merged on release/0.11.0,
so a maintainer can tag v0.11.2-rc.1.
@buluoray
buluoray requested review from a team and KiroCrewCaptain as code owners November 3, 2026 11:42
@buluoray
buluoray requested review from chenmingwei23 and removed request for a team November 3, 2026 11:42
@buluoray
buluoray merged commit 4e4aa88 into release/0.11.0 Nov 3, 2026
21 of 22 checks passed
@buluoray
buluoray deleted the crew/slack/release-0.11.2-rc1 branch November 3, 2026 11:42
@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: checking Automated validation is still running labels Nov 3, 2026
@github-actions

github-actions Bot commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5) — ✅ PASS

UX-level review of 2645ef1f4fa68766bcf269b07b653a69d12901fc — 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 strings and adds a CHANGELOG section. It adds or changes no user-visible control, so there are no screenshot gaps.

[UX-REVIEWED] 2645ef1

Description read

[DESCRIPTION-READ] de0ebc7e434f69decff59d5e7fb8667f4882f822dab39c067fbe69edd0aa4ca3

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

github-actions Bot commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ PASS

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

Design-Verdict: PASS

Nothing blocks: a routine RC version bump plus one prepended CHANGELOG section, the same shape as the 0.11.1 rc.1 PR.

[DESIGN-REVIEWED] 2645ef1

Description read

[DESCRIPTION-READ] 41fc8d276eb2878a2556401b0a1583693887d44e07a29228c99f3c63f9379f59

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

github-actions Bot commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — ✅ PASS

Premise-level review of 2645ef1f4fa68766bcf269b07b653a69d12901fc — 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 (2 items) — 2 justified

Intent: Let a maintainer tag v0.11.2-rc.1 so 0.11.1 users get the backported KAS and MCP fixes now. ADDITION (release bookkeeping).

  1. Desktop app, Python package and __version__ now report 0.11.2-rc.1 instead of 0.11.1 — justified
  2. CHANGELOG gains a ## [0.11.2] section describing the chore(release): backport the 0.11.2 hotfix fixes to release/0.11.0 #28835 backports, with every earlier section unchanged — justified

[FIRST-PRINCIPLES-REVIEWED] 2645ef1

Description read

[DESCRIPTION-READ] e37a80debe7285436c4b443e7e18bad584006b8e0676e14b41be6872f7ef0b0d

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

github-actions Bot commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

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

Review details

No findings.

[OPUS-REVIEWED] 2645ef1

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

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

@github-actions

github-actions Bot commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings

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

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 2645ef1

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

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