Skip to content

chore(release): drop 0.11.2-rc.1 to bare 0.11.2 - #29233

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

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

Conversation

@buluoray

@buluoray buluoray commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: Make release/0.11.0 declare 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.1 in all three version files. The stable-gate job refuses a bare v0.11.2 tag on a commit whose version files do not say 0.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

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.1 to 0.11.2 in src/kiro_crew/__init__.py, pyproject.toml and website/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.py and test/test_nightly_version_contract.py: 180 passed on this branch. scripts/check_changelog_history.py with CHANGELOG_BASE_REF=origin/release/0.11.0: OK.

Manual verification

grep for 0.11.2-rc in 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

  • 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

Contributed under the project's Apache-2.0 license.

@buluoray
buluoray requested review from a team and KiroCrewCaptain as code owners November 3, 2026 15:36
@buluoray
buluoray requested review from CrysisDeu and removed request for a team November 3, 2026 15:36
@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Nov 3, 2026
@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 8b87028280cf127c707f2ce2552c27ade2491fe1 — 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 (1 items) — 1 justified

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

  1. The package, CLI and desktop app report version 0.11.2 instead of 0.11.2-rc.1 — justified

[FIRST-PRINCIPLES-REVIEWED] 8b87028

Description read

[DESCRIPTION-READ] 629c49b2f3e4824be4302dc260bb15014e21e09efcfe063d9e7c2e1f88fc32b1

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

Design Review (Opus 5.5) — ✅ PASS

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

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 .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

Opus 5.5 Review — ✅ no blocking findings

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

Review details

No findings.

[OPUS-REVIEWED] 8b87028

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

False positive or not applicable? A repository writer can comment:
/ai-review override fable 8b87028280cf127c707f2ce2552c27ade2491fe1 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 8b87028280cf127c707f2ce2552c27ade2491fe1 and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 8b87028

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

@github-actions

github-actions Bot commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5) — ✅ PASS

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

UX-Verdict: PASS

Nothing to check. The diff changes only the version string from 0.11.2-rc.1 to 0.11.2 in three files and adds or changes no user-visible control, so the missing screenshots leave no evidence gap.

[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 .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 added readiness: passed Eligible automated validation passed for the current revision and removed readiness: checking Automated validation is still running labels Nov 3, 2026
@buluoray
buluoray merged commit 1d68676 into release/0.11.0 Nov 3, 2026
26 of 27 checks passed
@buluoray
buluoray deleted the crew/slack/release-0.11.2-stable branch November 3, 2026 16:05
@github-actions github-actions Bot removed the readiness: passed Eligible automated validation passed for the current revision label Nov 3, 2026
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