chore: release v6.0.0-rc.29#1172
Conversation
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
No actionable comments were generated in the recent review. 🎉 ℹ️ 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)
📝 WalkthroughWalkthroughThis PR bumps the crate version to 6.0.0-rc.29 and adds a ChangesRelease 6.0.0-rc.29
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 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: 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 `@RELEASE.md`:
- Around line 8-10: The RELEASE.md contains duplicate changelog headings "##
[Unreleased]" (new at the top) and "## [unreleased]" (existing later); remove or
normalize one so only a single canonical Unreleased heading remains (match
casing used across tooling). Locate the two headings ("## [Unreleased]" and "##
[unreleased]") and either delete the added duplicate or rename it to the
existing casing, ensuring only one Unreleased section exists in the file.
- Around line 48-49: The release note lists wreq-proto at version 0.2.1 but the
published manifest uses wreq-proto = "0.2.2"; update the RELEASE.md entry (the
bullet mentioning `wreq-proto`) to `0.2.2` so it matches the Cargo.toml, and
verify no other release notes or changelog lines reference the old 0.2.1
version.
🪄 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 will make changelog parsing ambiguous.
This adds ## [Unreleased] at the top while ## [unreleased] still exists at Line 162. Keep a single canonical heading/casing to avoid breaking release/changelog tooling.
🤖 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, The RELEASE.md contains duplicate changelog
headings "## [Unreleased]" (new at the top) and "## [unreleased]" (existing
later); remove or normalize one so only a single canonical Unreleased heading
remains (match casing used across tooling). Locate the two headings ("##
[Unreleased]" and "## [unreleased]") and either delete the added duplicate or
rename it to the existing casing, ensuring only one Unreleased section exists in
the file.
| - *(deps)* update `wreq-proto` dependency version to 0.2.1 ([#1163](https://github.com/0x676e67/wreq/pull/1163)) | ||
| - Enable git tagging in release configuration |
There was a problem hiding this comment.
Release note version for wreq-proto appears stale.
Line 48 says wreq-proto was updated to 0.2.1, but the same PR’s Cargo.toml uses wreq-proto = "0.2.2". Please align the note with the shipped manifest to avoid misleading users.
🤖 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 48 - 49, The release note lists wreq-proto at
version 0.2.1 but the published manifest uses wreq-proto = "0.2.2"; update the
RELEASE.md entry (the bullet mentioning `wreq-proto`) to `0.2.2` so it matches
the Cargo.toml, and verify no other release notes or changelog lines reference
the old 0.2.1 version.
0x676e67
force-pushed
the
release-plz-2026-05-08T13-59-24Z
branch
from
c40327a to
7d36126
Compare
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`:
- Line 43: Fix the malformed inline code on the release note line by wrapping
both symbol names in backticks and correcting the wording to read: rename
`OrigHeaderName` to `HeaderCaseName`; update the line that currently reads
"*(header)* rename `OrigHeaderName to `HeaderCaseName`" so both symbol names are
code spans and the sentence is well-formed (reference symbols: OrigHeaderName,
HeaderCaseName).
🪄 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: defaults
Review profile: CHILL
Plan: Pro
Run ID: b7172f7a-36fa-4edb-8f04-6ab55b715be7
📒 Files selected for processing (2)
Cargo.tomlRELEASE.md
✅ Files skipped from review due to trivial changes (1)
- Cargo.toml
|
|
||
| ### Other | ||
|
|
||
| - *(header)* rename `OrigHeaderName to `HeaderCaseName` ([#1174](https://github.com/0x676e67/wreq/pull/1174)) |
There was a problem hiding this comment.
Fix malformed inline code and rename wording.
Line 43 has broken backticks and reads incorrectly. It should consistently format both symbols as code spans.
✏️ Suggested fix
-- *(header)* rename `OrigHeaderName to `HeaderCaseName` ([`#1174`](https://github.com/0x676e67/wreq/pull/1174))
+- *(header)* rename `OrigHeaderName` to `HeaderCaseName` ([`#1174`](https://github.com/0x676e67/wreq/pull/1174))📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| - *(header)* rename `OrigHeaderName to `HeaderCaseName` ([#1174](https://github.com/0x676e67/wreq/pull/1174)) | |
| - *(header)* rename `OrigHeaderName` to `HeaderCaseName` ([`#1174`](https://github.com/0x676e67/wreq/pull/1174)) |
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 43-43: Spaces inside code span elements
(MD038, no-space-in-code)
🤖 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` at line 43, Fix the malformed inline code on the release note
line by wrapping both symbol names in backticks and correcting the wording to
read: rename `OrigHeaderName` to `HeaderCaseName`; update the line that
currently reads "*(header)* rename `OrigHeaderName to `HeaderCaseName`" so both
symbol names are code spans and the sentence is well-formed (reference symbols:
OrigHeaderName, HeaderCaseName).
7d36126 to
ed0d6f8
Compare
0x676e67
force-pushed
the
release-plz-2026-05-08T13-59-24Z
branch
from
ed0d6f8 to
22a690d
Compare
There was a problem hiding this comment.
♻️ Duplicate comments (2)
RELEASE.md (2)
45-45:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winFix malformed inline code spans in header rename note.
Line 45 has a broken code span. It should read:
rename \OrigHeaderName` to `HeaderCaseName``.✏️ Suggested fix
-- *(header)* rename `OrigHeaderName to `HeaderCaseName` ([`#1174`](https://github.com/0x676e67/wreq/pull/1174)) +- *(header)* rename `OrigHeaderName` to `HeaderCaseName` ([`#1174`](https://github.com/0x676e67/wreq/pull/1174))🤖 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` at line 45, The release note on line 45 has a malformed inline code span around the header names; update the text so the rename reads exactly as inline code for both symbols by enclosing each header identifier (OrigHeaderName and HeaderCaseName) in proper backticks so the line becomes: rename `OrigHeaderName` to `HeaderCaseName`.
8-8:⚠️ Potential issue | 🟠 Major | ⚡ Quick winConsolidate
Unreleasedheading casing to a single canonical section.Line 8 adds
## [Unreleased]while Line 165 still has## [unreleased]. Keep only one canonical heading/casing to avoid ambiguous changelog parsing.🤖 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` at line 8, There are two duplicate changelog headings with different casing: "## [Unreleased]" and "## [unreleased]"; pick one canonical heading (e.g., "## [Unreleased]") and remove or rename the other so only a single, consistently-cased Unreleased section remains; update any references if needed to match the chosen heading.
🤖 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.
Duplicate comments:
In `@RELEASE.md`:
- Line 45: The release note on line 45 has a malformed inline code span around
the header names; update the text so the rename reads exactly as inline code for
both symbols by enclosing each header identifier (OrigHeaderName and
HeaderCaseName) in proper backticks so the line becomes: rename `OrigHeaderName`
to `HeaderCaseName`.
- Line 8: There are two duplicate changelog headings with different casing: "##
[Unreleased]" and "## [unreleased]"; pick one canonical heading (e.g., "##
[Unreleased]") and remove or rename the other so only a single,
consistently-cased Unreleased section remains; update any references if needed
to match the chosen heading.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 360f2c65-6829-4206-a206-8e994bf6d932
📒 Files selected for processing (2)
Cargo.tomlRELEASE.md
✅ Files skipped from review due to trivial changes (1)
- Cargo.toml
0x676e67
force-pushed
the
release-plz-2026-05-08T13-59-24Z
branch
from
22a690d to
c616e92
Compare
|
excited for this! any timeline on when this may be released? TIA! |
|
Release soon? 👀 |
0x676e67
force-pushed
the
release-plz-2026-05-08T13-59-24Z
branch
from
c616e92 to
caebf8b
Compare
0x676e67
force-pushed
the
release-plz-2026-05-08T13-59-24Z
branch
from
caebf8b to
77f115c
Compare
3 participants
🤖 New release
wreq: 6.0.0-rc.28 -> 6.0.0-rc.29 (✓ API compatible changes)Changelog
This PR was generated with release-plz.