Skip to content

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

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

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

Conversation

@bolichen97

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: Start the 0.12.1 hotfix line on release/0.12.0: version 0.12.1-rc.1 and the ## [0.12.1] CHANGELOG section, so v0.12.1-rc.1 can be tagged.

The 0.12.1 hotfix backports (#33974, #34032, #34021, on top of the release owner's earlier batches) are merged on release/0.12.0, but the branch still declares 0.12.0 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.12.0 get these fixes only with the next minor.

Not a goal

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

What changed (motivation → approach → change)

Same shape as #29135 (0.11.2) and #26648 (0.11.1).

  • All three version files move from 0.12.0 to 0.12.1-rc.1: src/kiro_crew/__init__.py, pyproject.toml, website/electron/package.json.
  • CHANGELOG.md gains ## [0.12.1] - 2026-11-09, written from git log v0.12.0..release/0.12.0, 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 with CHANGELOG_BASE_REF=origin/release/0.12.0: 17 shipped sections intact.
  • The new section has one ## heading, ## [0.12.1] - 2026-11-09, on line 5, and no em or en dash.
  • The RC's release-candidate-tests run is the full verification; the release tree it builds equals the staging tree that already passed the whole backend suite and the AL2, AL2023 and macOS smoke.

Manual verification

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

Related Issues

Part of the 0.12.1 hot patch (#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.

…NGELOG)

Declare 0.12.1-rc.1 in the three version files and add the 0.12.1
CHANGELOG section, written from git log v0.12.0..release/0.12.0.
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