Repository navigation
chore(release): update changelog and bump version to 5.0.0 - #5594
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review.
|
| Layer / File(s) | Summary |
|---|---|
Version declarations and release notes Cargo.toml, package.json, packages/app-connect-contract/package.json, packages/bench-suite/package.json, packages/dapi-grpc/package.json, packages/dapi/package.json, packages/dash-spv/package.json, packages/dashmate/package.json, packages/dashpay-contract/package.json, packages/document-history-contract/package.json, packages/dpns-contract/package.json, packages/js-dapi-client/package.json, packages/js-dash-sdk/package.json, packages/js-evo-sdk/package.json, packages/js-grpc-common/package.json, packages/keyword-search-contract/package.json, packages/masternode-reward-shares-contract/package.json, packages/moderation-charters-contract/package.json, packages/platform-test-suite/package.json, packages/token-history-contract/package.json, packages/wallet-lib/package.json, packages/wallet-utils-contract/package.json, packages/wasm-dpp/package.json, packages/wasm-dpp2/package.json, packages/wasm-drive-verify/package.json, packages/wasm-sdk/package.json, packages/withdrawals-contract/package.json, CHANGELOG.md |
Workspace and package versions are updated to release values. The changelog adds the 5.0.0 entry with the listed fix and dependency updates. |
Priority:
Estimated code review effort: 1 (Trivial) | ~5 minutes
Change: Other
Possibly related PRs
- dashpay/platform#5583: Updates Tenderdash dependencies to v1.8.1, which the 5.0.0 changelog entry lists.
- dashpay/platform#5352: Implements the Android wallet-store opening fix listed in the changelog.
Suggested reviewers: shumkov
Merge Risk: 
Minimal · up to d7287
-
No actionable merge-blocking risk remains in this versioning-only release change.
Pre-merge checks: 
5
-
Full details: Docstring Coverage
-
Explanation
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (28 skipped: 28 unsupported.)
-
Finishing Touches: 💡 1
-
🛠️ Fix failing CI checks: 💡
-
- Commit to this branch
- Create a new PR
🧪 Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
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 help to get the list of available commands.
|
✅ Final review complete — Phase 1 only — no blockers (commit d7287cd) · triage: trivial |
|
Waiting for bot review — coderabbitai ✓ · thepastaclaw not yet. Wait for the missing reviews, or a writer can post |
thepastaclaw
left a comment
There was a problem hiding this comment.
Final review — Phase 1 only (trivial change)
This is a release-metadata-only change: package and workspace versions are bumped to 5.0.0, offset package majors are restored, and the changelog documents the three commits since v5.0.0-rc.8. The supplied review evidence confirms the version and lockfile changes are consistent, all completed code checks pass, and the remaining Rust and platform test checks are still in progress with no reported failures.
Review provenance
Source: reviewer 1: glm-5.3-flash (agent: phase1-reviewer, role: general); reviewer 2: glm-5.3-flash (agent: phase1-reviewer, role: architecture-layering); reviewer 3: glm-5.3-flash (agent: phase1-reviewer, role: platform-versioning); final verifier: gpt-6.1-sol (agent: sol-gate-verifier, role: final-verifier)
- Triage:
trivialbygpt-6.1-sol(effort low) — The diff only updates release metadata, package and crate versions, lockfile version lines, and the changelog without changing runtime behavior or protocol logic. - Phase 1 reviewers:
glm-5.3-flash— general (completed, effort high); agentphase1-reviewer,glm-5.3-flash— architecture-layering (completed, effort high); agentphase1-reviewer,glm-5.3-flash— platform-versioning (completed, effort high); agentphase1-reviewer - Phase 1 model:
glm-5.3-flash— zai quota: 5h 100% left, weekly 98% left; passed overgemini-3.8-flash-high(antigravity quota lookup failed) - Fresh verifier:
gpt-6.1-sol— final-verifier; agentsol-gate-verifier - Phase 2 reviewers: not run (triage rated this change trivial); this review comments and never approves
|
Bots are done — your move: post |
Brings 5.0.1 (v5.0-dev 093268c) into v5.1-dev: the 5.0.0 release (dashpay#5594, with dashpay#5352, dashpay#5582, dashpay#5583), dashpay#5557, dashpay#5558, dashpay#5560, dashpay#5561, dashpay#5559 and the 5.0.1 release bump (dashpay#5606). Conflict resolutions: - CHANGELOG.md: [Unreleased] on top, then the 5.0.1 and 5.0.0 entries. - rs-sdk error.rs: both sides added methods to Error; kept v5.1's consensus_error and dashpay#5560's spares_responder and into_exhausted_error. - rs-drive-abci tests/signed_response/mod.rs, moved from drive-proof-verifier by dashpay#5559: dashpay#5559's location, doc and drive_proof_verifier ContextProvider import, with v5.1's dpp::bls port. Semantic conflicts resolved: - rs-drive-abci tests/older_node_answers.rs (dashpay#5561): ported to dpp::bls, since v5.1-dev no longer ships blsful (dashpay#5320). The key is the scalar blsful's SecretKey::from_hash derived from the same label, so the public key and Basic-scheme signature bytes are unchanged. - rs-sdk protocol_gate_tests.rs (dashpay#5561): should_ask_a_fresh_sdk_network_for_its_version_once_then_send expected the SDK at 14 after its calls. The mock answers every expectation at the latest version, which was 14 on v5.0-dev and is 15 here, so the mocked fee-pots answers raise an unpinned SDK on to 15 (left: 15, right: 14). The test now expects the higher of 14 and the latest version; that the probe raised the SDK to 14 is shown by the first call being sent at all. Fails on the merge without this change, passes with it. Workspace and package versions follow v5.0-dev to 5.0.1, as the previous forward merges did. rust-dashcore stays on dev aca02026. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Basic explanation
What this does: Sets every package to version 5.0.0, the first stable release of Platform 5.0, and adds the 5.0.0 section to
CHANGELOG.md. Merging it, then publishing thev5.0.0GitHub release at the merge commit, builds the release assets.Value: This is the version mainnet nodes upgrade to. Once enough evonodes run it, mainnet activates protocol version 14.
Risks: Version numbers and the changelog only. No code changes.
Issue being fixed or feature implemented
Release new Dash Platform version 5.0.0.
What was done?
v5.0.0-rc.8, the newest prerelease of the 5.0 line, asfind_latest_tag.jsresolves for a stable release. It lists what merged since rc.8: fix(platform-wallet-storage): open the wallet store on Android #5352, chore: bump rustls-webpki and webpki-roots for RUSTSEC-2026-0381/0382/0383 #5582 and chore: bump rs-tenderdash-abci to v1.8.1 for zip RUSTSEC-2026-0367/0368/0369 #5583.package.json, every workspacepackage.json,[workspace.package]inCargo.toml, workspace crates inCargo.lock).yarn constraints --fix:@dashevo/dash-spv6.0.0,dash8.0.0,@dashevo/wallet-lib12.0.0.How Has This Been Tested?
yarn constraintspasses.cargo metadataresolves.Cargo.lockchanges only the version lines of the 48 workspace crates.Breaking Changes
None in this PR. The breaking changes of the 5.0 line are listed in the prerelease sections of
CHANGELOG.md.Checklist:
For repository code-owners and collaborators only
🤖 Generated with Claude Code
Summary by CodeRabbit
PR Hygiene ·
d7287cd/self-revieweddashmate(packages/dashmate/package.json) — ktechmidas or shumkovsystem-contracts— you own itjs-wasm-sdk(packages/js-dash-sdk/package.json,packages/js-evo-sdk/package.json,packages/wasm-sdk/package.json) — shumkovWhen every merge requirement is met, the
PR Hygienecheck passes. Reviewer limits do not block merging; other required GitHub checks and protections still apply.