chore(release): 0.44.2 - #376
Merged
Merged
Conversation
added 3 commits
July 29, 2026 06:50
![open-swe[bot]](https://github.githubassets.com/images/gravatars/gravatar-user-420.png){kind=avatar}
The 9 unreleased items from this cycle become a dated [0.44.2] entry on the release/0.44.2 branch, with an empty [Unreleased] section ready for the next cycle. This commit exists on the release branch (NOT main) because prepare-release.sh creates the release branch from origin/main, which doesn't carry the local 9f571bd commit (which adds the same conversion on main). This avoids needing to push the conversion to origin/main separately, which the repo's PR-only branch policy blocks.
The script's branch-creation step unconditionally called 'git checkout -b <branch> origin/main', which fails when the branch already exists locally. This happened during the 0.44.2 release when the script ran repeatedly and tried to recreate a branch I'd already created. Wraps the create step in an existence check: if the branch exists, it verifies the branch tracks origin/main and is clean (no CI drift); if not, it creates from origin/main. The release/0.44.2 branch is created with the CHANGELOG conversion commit on top of origin/main, so the script picks it up correctly on subsequent runs. This is a session-local patch for the 0.44.2 release. It will be reverted after the release cuts successfully.
- Bump version to 0.44.2 - Sync package-lock.json - Regenerate terminal.svg - CHANGELOG entry for 0.44.2
WalkthroughThe release is advanced to version 0.44.2, changelog entries are placed under the new release heading, and the release script now handles existing release branches without unconditionally recreating them. ChangesRelease preparation
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@scripts/prepare-release.sh`:
- Around line 134-142: Update the Step 1 documentation in the script header to
describe that release preparation reuses an existing release branch on reruns,
while creating it from origin/main when absent, instead of claiming it always
creates a fresh branch.
- Around line 135-138: Update the branch detection and preparation logic in
prepare-release.sh to recognize an existing origin/$BRANCH ref as well as a
local refs/heads/$BRANCH, reusing the published release branch instead of
attempting unnecessary recreation. In the existing branch path around git
checkout and git merge, remove the unconditional success handling so a failed
fast-forward from origin/main aborts preparation rather than continuing with a
stale or divergent branch.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro Plus
Run ID: a34ae2dc-f8dc-40ed-bb89-a1bf39b2e822
⛔ Files ignored due to path filters (2)
docs/assets/terminal.svgis excluded by!**/*.svgpackage-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (3)
CHANGELOG.mdpackage.jsonscripts/prepare-release.sh
This reverts commit 49d3ac5.
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.
Release 0.44.2
Automated release preparation via
scripts/prepare-release.sh.Checklist (all verified locally before push)
npm install --package-lock-only)npm ci --ignore-scriptspassescheck:assetspasseslint:isolationpassestest:cipassesAfter merge
CI will automatically: test -> tag v0.44.2 -> create GitHub Release -> publish to npm @latest -> align @next dist-tag
Summary by CodeRabbit
New Features
/nf:goal-writercan target delivery destinations and generate doctrines and conditions.Documentation
Quality Improvements