Skip to content

chore(release): bump release/0.12.0 to 0.12.0-rc.6 - #29151

Merged
buluoray merged 1 commit into
release/0.12.0from
crew/slack/release-0.12.0-rc6
Nov 3, 2026
Merged

buluoray merged 1 commit into
release/0.12.0from
crew/slack/release-0.12.0-rc6

Conversation

@buluoray

@buluoray buluoray commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: Declare 0.12.0-rc.6 on release/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.5 does not have it.

Not a goal

  • No other picks. No tag; a person pushes v0.12.0-rc.6 after this merges.
  • No CHANGELOG change.

What changed (motivation → approach → change)

All three version files (pyproject.toml, src/kiro_crew/__init__.py, website/electron/package.json) declare 0.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 no 0.12.0-rc.5 is left in them.

Related Issues

Follows #29148.

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.

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.
@buluoray
buluoray requested review from a team and KiroCrewCaptain as code owners November 3, 2026 12:09
@buluoray
buluoray requested review from mbriones98 and removed request for a team November 3, 2026 12:09
@buluoray
buluoray merged commit 0eee5c6 into release/0.12.0 Nov 3, 2026
17 checks passed
@buluoray
buluoray deleted the crew/slack/release-0.12.0-rc6 branch November 3, 2026 12:09
@github-actions

github-actions Bot commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ PASS

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

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

UX Review (Opus 5.5) — ✅ PASS

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

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 .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 c9951951dc18a1ad9003dcade67a8e1f61fb3169 — 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 (3 items) — 3 justified

Intent: let insider users get the 0.11.2 fixes forward-ported in #29148 by declaring the next RC, 0.12.0-rc.6. This is a FIX.

  1. The Python package reports version 0.12.0-rc.6 (in pyproject.toml) — justified
  2. kiro_crew.__version__ reports 0.12.0-rc.6 — justified
  3. The desktop app reports version 0.12.0-rc.6 (in Electron's package.json) — justified

[FIRST-PRINCIPLES-REVIEWED] c995195

Description read

[DESCRIPTION-READ] 15b4f870973c2e97ce956bd7e4adb073adf9af1cfe0b8dc6efb2544be8954d70

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 c9951951dc18a1ad9003dcade67a8e1f61fb3169 — this comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] c995195

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

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

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] c995195

False positive or not applicable? A repository writer can comment:
/ai-review override gpt c9951951dc18a1ad9003dcade67a8e1f61fb3169 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