chore: release v6.0.0-rc.29 - #1162
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:
📝 WalkthroughWalkthroughBump crate version in Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 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 docstrings
🧪 Generate unit tests (beta)
Warning Review ran into problems🔥 ProblemsGit: Failed to clone repository. Please run the 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.
🧹 Nitpick comments (1)
RELEASE.md (1)
10-10: Optional: confirm date/compare range accuracy.The
6.0.0-rc.29compare link and date are consistent with the release bump, but it’d be worth confirming the publish date is truly2026-04-29and the compare range is correct for your tagging/release process.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@RELEASE.md` at line 10, Verify and, if necessary, correct the release header string "## [6.0.0-rc.29](https://github.com/0x676e67/wreq/compare/v6.0.0-rc.28...v6.0.0-rc.29) - 2026-04-29": confirm the published release date is truly 2026-04-29 and that the GitHub compare range uses the correct previous tag (v6.0.0-rc.28) and current tag (v6.0.0-rc.29); if either is wrong, update the date or the compare URL accordingly so the header accurately reflects the actual tag names and publish date.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@RELEASE.md`:
- Line 10: Verify and, if necessary, correct the release header string "##
[6.0.0-rc.29](https://github.com/0x676e67/wreq/compare/v6.0.0-rc.28...v6.0.0-rc.29)
- 2026-04-29": confirm the published release date is truly 2026-04-29 and that
the GitHub compare range uses the correct previous tag (v6.0.0-rc.28) and
current tag (v6.0.0-rc.29); if either is wrong, update the date or the compare
URL accordingly so the header accurately reflects the actual tag names and
publish date.
1b467bb to
359e701
Compare
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
359e701 to
589900d
Compare
589900d to
616db0d
Compare
616db0d to
8cc7e16
Compare
There was a problem hiding this comment.
♻️ Duplicate comments (1)
RELEASE.md (1)
8-8:⚠️ Potential issue | 🟡 MinorConsolidate duplicate unreleased sections.
Line 8 introduces
## [Unreleased], but another unreleased block still exists at Line 156 (## [unreleased]). Please merge into a single canonical section to avoid split/stale pre-release notes.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@RELEASE.md` at line 8, There are two duplicate release headers ("## [Unreleased]" and "## [unreleased]")—merge them into a single canonical section: pick one header casing (e.g., "## [Unreleased]"), combine the content under both headers into that single header preserving chronological order and any sub-entries, remove the other duplicate header and its empty spacing, and ensure there is only one "Unreleased" section in RELEASE.md so pre-release notes are not split or stale.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Duplicate comments:
In `@RELEASE.md`:
- Line 8: There are two duplicate release headers ("## [Unreleased]" and "##
[unreleased]")—merge them into a single canonical section: pick one header
casing (e.g., "## [Unreleased]"), combine the content under both headers into
that single header preserving chronological order and any sub-entries, remove
the other duplicate header and its empty spacing, and ensure there is only one
"Unreleased" section in RELEASE.md so pre-release notes are not split or stale.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: e78b5bd8-9f92-42b3-99c7-9621cc382b18
📒 Files selected for processing (2)
Cargo.tomlRELEASE.md
✅ Files skipped from review due to trivial changes (1)
- Cargo.toml
8cc7e16 to
93475f2
Compare
93475f2 to
72aad33
Compare
72aad33 to
887887b
Compare
887887b to
3e75723
Compare
3e75723 to
96d3a93
Compare
* chore(trust): improve unreachable branch in certificate loading * fmt
96d3a93 to
d94dd10
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.