chore: release v6.0.0-rc.29#1171
Conversation
|
ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✅ Files skipped from review due to trivial changes (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughThis pull request prepares the v6.0.0-rc.29 release by incrementing the crate version in ChangesRelease v6.0.0-rc.29 Preparation
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 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: 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 `@RELEASE.md`:
- Around line 8-10: There are two duplicate unreleased headings ("##
[Unreleased]" and "## [unreleased]") in RELEASE.md which makes the changelog
ambiguous; locate both headings and merge any entries under a single canonical
"## [Unreleased]" section (pick one heading style and remove the other), moving
all pending/unreleased entries into that single section and ensuring that the
versioned heading "## [6.0.0-rc.29]" and other released headings contain only
released items; update capitalization to be consistent and delete the now-empty
duplicate heading so the file has one clear Unreleased section.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
| ## [Unreleased] | ||
|
|
||
| ## [6.0.0-rc.29](https://github.com/0x676e67/wreq/compare/v6.0.0-rc.28...v6.0.0-rc.29) - 2026-05-08 |
There was a problem hiding this comment.
Duplicate “Unreleased” sections make changelog state ambiguous.
Line 8 adds a new ## [Unreleased], but there is still another ## [unreleased] section at Line 161 containing entries. Please consolidate to a single unreleased section (and ensure released content is only under versioned headings) before merging.
🤖 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 `@RELEASE.md` around lines 8 - 10, There are two duplicate unreleased headings
("## [Unreleased]" and "## [unreleased]") in RELEASE.md which makes the
changelog ambiguous; locate both headings and merge any entries under a single
canonical "## [Unreleased]" section (pick one heading style and remove the
other), moving all pending/unreleased entries into that single section and
ensuring that the versioned heading "## [6.0.0-rc.29]" and other released
headings contain only released items; update capitalization to be consistent and
delete the now-empty duplicate heading so the file has one clear Unreleased
section.
0x676e67
force-pushed
the
release-plz-2026-05-08T12-14-31Z
branch
from
9d35d6a to
27327d5
Compare
1 participant
🤖 New release
wreq: 6.0.0-rc.28 -> 6.0.0-rc.29 (✓ API compatible changes)Changelog
This PR was generated with release-plz.
Summary by CodeRabbit