chore(release): prepare 0.29.0 - #53
Merged
Merged
Conversation
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (8)
📝 WalkthroughWalkthroughBumps project and package versions to 0.29.0/1.2.0, inserts 0.29.0 release headings under Unreleased, and updates README, Quick Start, and Linux installer docs to reference 0.29.0 artifacts and checksums. ChangesRelease 0.29.0
🎯 2 (Simple) | ⏱️ ~10 minutes Suggested labels: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 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 `@docs/en/release-notes/changelog.md`:
- Around line 20-21: The docs page docs/en/release-notes/changelog.md has an
empty "## 0.29.0 (2026-06-01)" heading while the root CHANGELOG.md contains the
four 0.29.0 entries; re-run or repair the changelog auto-sync process so the "##
0.29.0 (2026-06-01)" section in docs/en/release-notes/changelog.md is populated
from the root CHANGELOG.md (do not edit the docs file manually), verify the sync
tool includes all four 0.29.0 bullets and commit the regenerated docs file so
the headings and entries match.
🪄 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: ASSERTIVE
Plan: Pro Plus
Run ID: 4c224b07-59d2-467c-84b7-ec9196ee54f1
⛔ Files ignored due to path filters (1)
uv.lockis excluded by!**/*.lock
📒 Files selected for processing (7)
CHANGELOG.mdREADME.mddocs/en/guides/getting-started.mddocs/en/release-notes/breaking-changes.mddocs/en/release-notes/changelog.mdpackages/linux-installer/README.mdpyproject.toml
elkaix
force-pushed
the
release/0.29.0
branch
2 times, most recently
from
June 2, 2026 03:55
9a8e525 to
c0e960e
Compare
Contributor
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
packages/linux-installer/README.md (1)
38-40:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winUpdate local build example to the current release version.
The build command still uses
0.28.0while the rest of this document now targets0.29.0.Suggested fix
-bash packages/linux-installer/build.sh 0.28.0 +bash packages/linux-installer/build.sh 0.29.0🤖 Prompt for 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. In `@packages/linux-installer/README.md` around lines 38 - 40, Update the example build command in the README to use the current release version: change the shown invocation of the build script (bash packages/linux-installer/build.sh 0.28.0) to the correct version (0.29.0) so the README’s local build example matches the rest of the document and the project's current release.CHANGELOG.md (1)
41-41:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winFix wrong upgrade version in the 0.29.0 section.
Line 41 still points to
pythinker-code==0.28.0; it should reference0.29.0for this release block.Suggested fix
-Upgrade with `pythinker update`, `pip install --upgrade pythinker-code==0.28.0`, or use the native installer for your OS (see the README install table). +Upgrade with `pythinker update`, `pip install --upgrade pythinker-code==0.29.0`, or use the native installer for your OS (see the README install table).🤖 Prompt for 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. In `@CHANGELOG.md` at line 41, Update the version string in the 0.29.0 changelog entry: replace the incorrect `pythinker-code==0.28.0` reference with `pythinker-code==0.29.0` in CHANGELOG.md so the upgrade instruction correctly targets the 0.29.0 release.
🤖 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.
Outside diff comments:
In `@CHANGELOG.md`:
- Line 41: Update the version string in the 0.29.0 changelog entry: replace the
incorrect `pythinker-code==0.28.0` reference with `pythinker-code==0.29.0` in
CHANGELOG.md so the upgrade instruction correctly targets the 0.29.0 release.
In `@packages/linux-installer/README.md`:
- Around line 38-40: Update the example build command in the README to use the
current release version: change the shown invocation of the build script (bash
packages/linux-installer/build.sh 0.28.0) to the correct version (0.29.0) so the
README’s local build example matches the rest of the document and the project's
current release.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: ba4ceb13-0906-4ae9-aa51-e80fdac68cee
⛔ Files ignored due to path filters (1)
uv.lockis excluded by!**/*.lock
📒 Files selected for processing (8)
CHANGELOG.mdREADME.mddocs/en/guides/getting-started.mddocs/en/release-notes/breaking-changes.mddocs/en/release-notes/changelog.mdpackages/linux-installer/README.mdpackages/pythinker-core/pyproject.tomlpyproject.toml
This was referenced Jun 2, 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
1 participant
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.
Automated release prep for 0.29.0, including pythinker-core 1.2.0.
After merge, publish the core package first, wait for PyPI, then publish the root release.
Tag sequence after merge:
Summary by CodeRabbit