Repository navigation
chore(release): start the 0.12.1 hotfix line (0.12.1-rc.1 and its CHANGELOG) - #34033
Merged
Merged
Conversation
…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.
This was referenced Nov 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem / Motivation
Goal: Start the 0.12.1 hotfix line on
release/0.12.0: version0.12.1-rc.1and the## [0.12.1]CHANGELOG section, sov0.12.1-rc.1can 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 declares0.12.0and 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
0.12.1(that is a later PR).main; the 0.12.1 section is ported tomainwhen 0.12.1 reaches stable.What changed (motivation → approach → change)
Same shape as #29135 (0.11.2) and #26648 (0.11.1).
0.12.0to0.12.1-rc.1:src/kiro_crew/__init__.py,pyproject.toml,website/electron/package.json.CHANGELOG.mdgains## [0.12.1] - 2026-11-09, written fromgit log v0.12.0..release/0.12.0, as one opening paragraph and a### Notable fixestail 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.pywithCHANGELOG_BASE_REF=origin/release/0.12.0: 17 shipped sections intact.##heading,## [0.12.1] - 2026-11-09, on line 5, and no em or en dash.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
feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)Contribution License Agreement
Contributions are accepted under the project's Apache-2.0 license; see the Licensing section of CONTRIBUTING.md.