Skip to content

chore(release): drop 0.12.1-rc.1 to bare 0.12.1 - #34035

Merged
bolichen97 merged 1 commit into
release/0.12.0from
hotfix/0.12.1-stable
Nov 9, 2026
Merged

bolichen97 merged 1 commit into
release/0.12.0from
hotfix/0.12.1-stable

Conversation

@bolichen97

@bolichen97 bolichen97 commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: Make release/0.12.0 declare the bare version 0.12.1, so the 0.12.1 hotfix can be promoted to stable.

The release branch declares 0.12.1-rc.1 in all three version files. The stable-gate job refuses a bare v0.12.1 tag on a commit whose version files do not say 0.12.1 (docs/build/release.md, "Runbook: promoting an RC to stable", step 1).

Why it matters

Without this change, the 0.12.1 hotfix cannot ship to stable. Stable users stay on 0.12.0 without its fixes.

Not a goal

What changed (motivation → approach → change)

Goal: a promotion candidate for 0.12.1 -> approach: step 1 of the documented runbook, the version drop -> change: 0.12.1-rc.1 to 0.12.1 in src/kiro_crew/__init__.py, pyproject.toml and website/electron/package.json. This is the same change as the 0.11.2 drop (#29233) and 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: run by the gate RC's release-candidate-tests on this commit, as for the 0.11.2 drop. scripts/check_changelog_history.py with CHANGELOG_BASE_REF=origin/release/0.12.0: the CHANGELOG is unchanged by this PR (17 shipped sections intact at the version PR).

Manual verification

grep for 0.12.1-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.12.1 hot patch (#34033, #33974, #34032, #34021).

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.

Release step 1 of the documented promotion: the three version files
declare the bare 0.12.1, so the gate RC cut on this commit is a
promotion candidate and stable-gate accepts a bare v0.12.1 tag here.
@bolichen97
bolichen97 requested review from a team and KiroCrewCaptain as code owners November 9, 2026 18:12
@bolichen97
bolichen97 requested review from Zedmor and removed request for a team November 9, 2026 18:12
@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ⚠️ review incomplete

GPT 6.1 did not produce a complete verdict for eba1ef319b4b96f0c97d34db61f187a64ec8205f; inspect the workflow logs and re-run it.

This comment is updated in place on each push.

See the GPT 6.1 Review job logs; this commit has no completed GPT verdict.

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

@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — ✅ PASS

Premise-level review of eba1ef319b4b96f0c97d34db61f187a64ec8205f — 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.12.1 hotfix to stable by declaring the bare version. This is a FIX (release step).

  1. The declared package, CLI and desktop version changes from 0.12.1-rc.1 to 0.12.1 in all three version files — justified

[FIRST-PRINCIPLES-REVIEWED] eba1ef3

Description read

[DESCRIPTION-READ] 6d53768fc933d8a37e03cf809cee25db0cd1271fee82725a55f85a0dcf96c598

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 9, 2026

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5) — ✅ PASS

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

UX-Verdict: PASS

Nothing to check. The PR changes only the version string, from 0.12.1-rc.1 to 0.12.1, in three files. It adds or changes no control, label or state anyone sees in the product.

[UX-REVIEWED] eba1ef3

Description read

[DESCRIPTION-READ] 514fe0aa0d94e298dbb23d5ca512ab44067124568935b48daa6de2674be1e090

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 9, 2026

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ PASS

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

Design-Verdict: PASS

Nothing blocks. This is the documented runbook's version drop. No 0.12.1-rc string is left anywhere in the tree.

Notes

  • The ## Tests section still has the template placeholders {{N}} passed and {{OK}}, so the gate results it claims were never recorded. Fill in the real counts before you merge.

[DESIGN-REVIEWED] eba1ef3

Description read

[DESCRIPTION-READ] ddcb57c491785ce13485a272de2661837d661e56db085aa2790cb896dcd6e39f

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.

@bolichen97
bolichen97 merged commit 87fc8e4 into release/0.12.0 Nov 9, 2026
12 of 13 checks passed
@bolichen97
bolichen97 deleted the hotfix/0.12.1-stable branch November 9, 2026 18:14
@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

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

Review details

No findings.

[OPUS-REVIEWED] eba1ef3

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

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