chore(release): update changelog and bump version to 3.0.0-rc.3#3006
Conversation
📝 WalkthroughWalkthroughA coordinated version bump release changing version identifiers from RC.2 to RC.3 across the workspace. Updates include a new CHANGELOG entry documenting features and bug fixes, workspace configuration update via Cargo.toml, and version field updates across approximately 24 package.json files with varying version schemes. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 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 |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Fix all issues with AI agents
In `@CHANGELOG.md`:
- Around line 6-12: Replace the broken placeholder issue links in the CHANGELOG
entries for the bullets that mention "**dashmate:** add Let's Encrypt SSL
provider support", "**drive:** improve error handling in merk proof extraction",
and "**platform:** update grovedb dependency to allow for larger proof sizes"
with actual GitHub issue or PR URLs (e.g.
https://github.com/<owner>/<repo>/issues/<num> or /pull/<num>) so the links
resolve; update each Markdown link target from the current undefined/... to the
correct full GitHub URL while keeping the existing display text unchanged.
- Line 1: The release header contains an invalid compare link "##
[3.0.0-rc.3](///compare/v3.0.0-rc.2...v3.0.0-rc.3) (2026-01-20)"; replace the
"///compare/v3.0.0-rc.2...v3.0.0-rc.3" target with the repo's full compare URL
(e.g., use the https://github.com/OWNER/REPO/compare/v3.0.0-rc.2...v3.0.0-rc.3
pattern) so the markdown link renders correctly for the "## [3.0.0-rc.3](...)"
header.
| @@ -1,3 +1,16 @@ | |||
| ## [3.0.0-rc.3](///compare/v3.0.0-rc.2...v3.0.0-rc.3) (2026-01-20) | |||
There was a problem hiding this comment.
Fix the compare URL (currently invalid).
///compare/... will render as a broken link in most markdown renderers; use the repo’s full compare URL format for consistency with other entries.
🛠️ Suggested fix
-## [3.0.0-rc.3](///compare/v3.0.0-rc.2...v3.0.0-rc.3) (2026-01-20)
+## [3.0.0-rc.3](https://github.com/dashpay/platform/compare/v3.0.0-rc.2...v3.0.0-rc.3) (2026-01-20)📝 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.
| ## [3.0.0-rc.3](///compare/v3.0.0-rc.2...v3.0.0-rc.3) (2026-01-20) | |
| ## [3.0.0-rc.3](https://github.com/dashpay/platform/compare/v3.0.0-rc.2...v3.0.0-rc.3) (2026-01-20) |
🤖 Prompt for AI Agents
In `@CHANGELOG.md` at line 1, The release header contains an invalid compare link
"## [3.0.0-rc.3](///compare/v3.0.0-rc.2...v3.0.0-rc.3) (2026-01-20)"; replace
the "///compare/v3.0.0-rc.2...v3.0.0-rc.3" target with the repo's full compare
URL (e.g., use the
https://github.com/OWNER/REPO/compare/v3.0.0-rc.2...v3.0.0-rc.3 pattern) so the
markdown link renders correctly for the "## [3.0.0-rc.3](...)" header.
| * **dashmate:** add Let's Encrypt SSL provider support ([#3000](undefined/undefined/undefined/issues/3000)) | ||
| * **drive:** improve error handling in merk proof extraction ([#3003](undefined/undefined/undefined/issues/3003)) | ||
|
|
||
|
|
||
| ### Bug Fixes | ||
|
|
||
| * **platform:** update grovedb dependency to allow for larger proof sizes ([#3005](undefined/undefined/undefined/issues/3005)) |
There was a problem hiding this comment.
Issue links are broken (undefined/...).
The new bullet links won’t resolve; please replace with real GitHub issue URLs (or PR links) like other entries.
🛠️ Suggested fix
-* **dashmate:** add Let's Encrypt SSL provider support ([`#3000`](undefined/undefined/undefined/issues/3000))
-* **drive:** improve error handling in merk proof extraction ([`#3003`](undefined/undefined/undefined/issues/3003))
+* **dashmate:** add Let's Encrypt SSL provider support ([`#3000`](https://github.com/dashpay/platform/issues/3000))
+* **drive:** improve error handling in merk proof extraction ([`#3003`](https://github.com/dashpay/platform/issues/3003))
...
-* **platform:** update grovedb dependency to allow for larger proof sizes ([`#3005`](undefined/undefined/undefined/issues/3005))
+* **platform:** update grovedb dependency to allow for larger proof sizes ([`#3005`](https://github.com/dashpay/platform/issues/3005))📝 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.
| * **dashmate:** add Let's Encrypt SSL provider support ([#3000](undefined/undefined/undefined/issues/3000)) | |
| * **drive:** improve error handling in merk proof extraction ([#3003](undefined/undefined/undefined/issues/3003)) | |
| ### Bug Fixes | |
| * **platform:** update grovedb dependency to allow for larger proof sizes ([#3005](undefined/undefined/undefined/issues/3005)) | |
| * **dashmate:** add Let's Encrypt SSL provider support ([`#3000`](https://github.com/dashpay/platform/issues/3000)) | |
| * **drive:** improve error handling in merk proof extraction ([`#3003`](https://github.com/dashpay/platform/issues/3003)) | |
| ### Bug Fixes | |
| * **platform:** update grovedb dependency to allow for larger proof sizes ([`#3005`](https://github.com/dashpay/platform/issues/3005)) |
🤖 Prompt for AI Agents
In `@CHANGELOG.md` around lines 6 - 12, Replace the broken placeholder issue links
in the CHANGELOG entries for the bullets that mention "**dashmate:** add Let's
Encrypt SSL provider support", "**drive:** improve error handling in merk proof
extraction", and "**platform:** update grovedb dependency to allow for larger
proof sizes" with actual GitHub issue or PR URLs (e.g.
https://github.com/<owner>/<repo>/issues/<num> or /pull/<num>) so the links
resolve; update each Markdown link target from the current undefined/... to the
correct full GitHub URL while keeping the existing display text unchanged.
Issue being fixed or feature implemented
Release new Dash Platform version
What was done?
How Has This Been Tested?
None
Breaking Changes
None
Checklist:
For repository code-owners and collaborators only
Summary by CodeRabbit
New Features
Bug Fixes
Chores
✏️ Tip: You can customize this high-level summary in your review settings.