Skip to content

chore(release): start the 0.9.0 insider line - #18356

Merged
bolichen97 merged 1 commit into
release/0.9.0from
release/0.9.0-cut
Oct 9, 2026
Merged

bolichen97 merged 1 commit into
release/0.9.0from
release/0.9.0-cut

Conversation

@KiroCrewCaptain

Copy link
Copy Markdown
Collaborator

What

Start the 0.9.0 insider line on release/0.9.0:

  • All three version files move from the bare 0.9.0 that main carries to the dual-valid RC spelling 0.9.0-rc.1: src/kiro_crew/__init__.py, pyproject.toml and website/electron/package.json. The website/electron/package-lock.json root still reads 0.7.0, as it does on main and release/0.8.0; it is not one of the three declaration files and is left alone.
  • CHANGELOG.md gains ## [0.9.0] - 2026-10-09 above [0.8.0]. Nothing else in the file changes.

Why

The version numbering policy in docs/build/release.md says an insider release branch declares X.Y.Z-rc.N in all three files, and the RC runbook says the branch carries its ## [X.Y.Z] - <date> section, with no [Unreleased], at the RC cut. release/0.9.0 was cut from main and still declared the bare 0.9.0 with no 0.9.0 section.

CHANGELOG range

35fac2012914f17dad3195a1f472d6df1c72a6ee (merge-base of release/0.8.0 and the branch head) ..69dc0ceee3d2812c43078cebbd2ae8431ee245a4, first-parent: 1636 commits.

The section follows docs/build/changelog.md: an opening paragraph, twelve subsections of at most three one-sentence bullets, two marked (Preview), and a Notable fixes section of three short paragraphs. It has no Before you upgrade and no Contributors section, and no em or en dash.

The 0.8.0 section

Unchanged. The [0.8.0] section on this branch is already the final one: extracted from ## [0.8.0] to the next ## [ heading, it is byte-identical to the one on release/0.8.0 at 4d205dadc142500dd3f0e89de28ce70304b72d7c (529 lines, empty diff).

Checks run on the head of this branch:

  • CHANGELOG_BASE_REF=origin/release/0.9.0 python3 scripts/check_changelog_history.py: 12 shipped section(s) at origin/release/0.9.0 are intact at head OK.
  • python3 scripts/check_changelog_history.py: no draft sections OK.
  • pytest on test_stable_version_display.py, test_stable_release_gate.py, test_changelog_parse.py, test_changelog_history_gate.py, test_release_channel.py, test_build_version_override.py, test_cli_version_fastpath.py and test_kiro_crew.py: 276 passed.

After merge

A maintainer pushes an annotated tag v0.9.0-insider.1 on the merge commit, with the message KiroCrew 0.9.0 insider candidate 1. Do not push v0.9.0-rc.N tags on this base: an rc.N and an insider.N tag with the same number map to the same wheel version.

Pattern harvest

Not generalizable: release branch cut with no defect behind it.

…GELOG)

Declare the release/0.9.0 branch identity as the dual-valid RC spelling the version numbering policy requires on an insider release branch: all three version files move from the bare 0.9.0 main carries to 0.9.0-rc.1. Add the ## [0.9.0] - 2026-10-09 section, written from the range 35fac20..69dc0ce minus the commits backported to release/0.8.0. Every earlier section is unchanged.
@KiroCrewCaptain
KiroCrewCaptain requested a review from a team as a code owner October 9, 2026 06:02
@KiroCrewCaptain
KiroCrewCaptain requested review from CrysisDeu and removed request for a team October 9, 2026 06:02
@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Oct 9, 2026
@github-actions

github-actions Bot commented Oct 9, 2026

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — ✅ PASS

Premise-level review of 2aaf246dbf16dcf9dfab9ec7f0e66b8de96bfac3 — 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/CONCERNS are advisory.

First-Principles-Verdict: PASS

Check before tagging: the post-merge step says to push v0.9.0-insider.1, but docs/build/release.md:653-655 says the branch's "tags vX.Y.Z-rc.N" (and line 644 says "Stick to one convention (-rc.N) per base version").

What this change ships

Inventory (2 items) — 2 justified

Intent: open the 0.9.0 insider line so its builds identify as release candidate 1 and its release notes exist at the cut (an ADDITION; this is release chore work).

  1. A non-tag build of the release branch now reports 0.9.0-rc.1 instead of the bare 0.9.0, the same in all three version files. — justified
  2. The changelog gains a [0.9.0] - 2026-10-09 section above [0.8.0], and every earlier section stays byte-identical. — justified

[FIRST-PRINCIPLES-REVIEWED] 2aaf246

Description read

[DESCRIPTION-READ] 90463be5b185645633b48188e7f852fc77f5eed01707f200ff4711b390c778d0

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

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ PASS

Design-level review of 2aaf246dbf16dcf9dfab9ec7f0e66b8de96bfac3 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

Design-Verdict: PASS

Check that the tag scheme is settled: release.md's policy says to tag vX.Y.Z-rc.N, but this PR tells maintainers to tag v0.9.0-insider.1, as 0.8.0 did.

[DESIGN-REVIEWED] 2aaf246

Description read

[DESCRIPTION-READ] 1372c5fc5d2df15c6ceb597834e09d044ca35e997eb46e5daf0b0e3381f1c631

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

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings

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

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 2aaf246

False positive or not applicable? A repository writer can comment:
/ai-review override gpt 2aaf246dbf16dcf9dfab9ec7f0e66b8de96bfac3: <one-sentence reason>

@github-actions

github-actions Bot commented Oct 9, 2026

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5) — ✅ PASS

UX-level review of 2aaf246dbf16dcf9dfab9ec7f0e66b8de96bfac3 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

UX-Verdict: PASS

Check that the About dialog and the update prompt show 0.9.0-rc.1 as an insider build, not as a stable 0.9.0.

[UX-REVIEWED] 2aaf246

Description read

[DESCRIPTION-READ] bb02512abd58a53800461b6919c45870b913a8e82aa19891b945c8e2b5bfca28

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

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

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

Review details

No findings.

[OPUS-REVIEWED] 2aaf246

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

False positive or not applicable? A repository writer can comment:
/ai-review override fable 2aaf246dbf16dcf9dfab9ec7f0e66b8de96bfac3: <one-sentence reason>

@bolichen97
bolichen97 merged commit 13a24b1 into release/0.9.0 Oct 9, 2026
24 of 26 checks passed
@bolichen97
bolichen97 deleted the release/0.9.0-cut branch October 9, 2026 06:31
@github-actions github-actions Bot removed the readiness: checking Automated validation is still running label Oct 9, 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.

2 participants