Skip to content

chore(release): update changelog and bump version to 5.0.0 - #5594

Merged
QuantumExplorer merged 1 commit into
v5.0-devfrom
release_5.0.0
Oct 26, 2026
Merged

QuantumExplorer merged 1 commit into
v5.0-devfrom
release_5.0.0

Conversation

@QuantumExplorer

@QuantumExplorer QuantumExplorer commented Oct 26, 2026 •

Copy link
Copy Markdown
Member

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 the v5.0.0 GitHub 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?

How Has This Been Tested?

  • yarn constraints passes.
  • cargo metadata resolves. Cargo.lock changes 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:

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have added or updated relevant unit/integration/functional/e2e tests
  • I have made corresponding changes to the documentation

For repository code-owners and collaborators only

  • I have assigned this pull request to a milestone

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Bug Fixes
    • Fixed an issue that could prevent the Android wallet store from opening.
  • Security
    • Updated dependencies to address reported security advisories.
  • Release
    • Released version 5.0.0.

PR Hygiene · d7287cd

  • Bots — coderabbitai ✓ · thepastaclaw ✓
  • Self-review — post /self-reviewed
  • Reviewer requests paused — your 5 review slots are occupied; this PR is excluded from reviewers' queues. Required approvals still count without a slot.
  • Build running
  • Approvals
    • files with no dedicated owner — you own it
    • dashmate (packages/dashmate/package.json) — ktechmidas or shumkov
    • system-contracts — you own it
    • js-wasm-sdk (packages/js-dash-sdk/package.json, packages/js-evo-sdk/package.json, packages/wasm-sdk/package.json) — shumkov

When every merge requirement is met, the PR Hygiene check passes. Reviewer limits do not block merging; other required GitHub checks and protections still apply.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@QuantumExplorer QuantumExplorer added this to the v5.0.0 milestone Oct 26, 2026
@coderabbitai

coderabbitai Bot commented Oct 26, 2026 •

Copy link
Copy Markdown
Contributor

Review in Change Stack →

No actionable comments were generated in the recent review.

Recent review info
Run configuration
Commits

Reviewing files that changed from the base of the PR and between f63dbfd and d7287cd.

Files ignored due to path filters: 1
  • Cargo.lock is excluded by !**/*.lock
Files selected for processing: 28
  • CHANGELOG.md
  • 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

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

Walkthrough

The workspace and package versions move from release-candidate values to release values. The changelog adds a 5.0.0 entry listing an Android wallet-store fix and dependency updates.

Changes: Release versioning

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: Normal

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Possibly related PRs

Suggested reviewers: shumkov

Merge Risk: Minimal · up to d7287

No actionable merge-blocking risk remains in this versioning-only release change.

Pre-merge checks: Passed 5
Check name Status Explanation
Description Check Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check Passed The title clearly and concisely describes the main changes: updating the changelog and bumping package versions to 5.0.0.
Docstring Coverage Passed 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…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@thepastaclaw

thepastaclaw commented Oct 26, 2026 •

Copy link
Copy Markdown
Collaborator

✅ Final review complete — Phase 1 only — no blockers (commit d7287cd) · triage: trivial

@github-actions

github-actions Bot commented Oct 26, 2026 •

Copy link
Copy Markdown
Contributor

Waiting for bot review — coderabbitai ✓ · thepastaclaw not yet. Wait for the missing reviews, or a writer can post /skip-bots to proceed without them; blocking findings still need addressing.
Full checklist in the description.

@github-actions github-actions Bot added the waiting-bots Waiting for the review bots to report on this head label Oct 26, 2026

@thepastaclaw thepastaclaw left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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: trivial by gpt-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); agent phase1-reviewer, glm-5.3-flash — architecture-layering (completed, effort high); agent phase1-reviewer, glm-5.3-flash — platform-versioning (completed, effort high); agent phase1-reviewer
  • Phase 1 model: glm-5.3-flash — zai quota: 5h 100% left, weekly 98% left; passed over gemini-3.8-flash-high (antigravity quota lookup failed)
  • Fresh verifier: gpt-6.1-sol — final-verifier; agent sol-gate-verifier
  • Phase 2 reviewers: not run (triage rated this change trivial); this review comments and never approves

@github-actions

Copy link
Copy Markdown
Contributor

Bots are done — your move: post /self-reviewed.
Full checklist in the description.

@github-actions github-actions Bot added waiting-self-review Waiting for the author to post /self-reviewed and removed waiting-bots Waiting for the review bots to report on this head labels Oct 26, 2026
@QuantumExplorer
QuantumExplorer merged commit 389dd6a into v5.0-dev Oct 26, 2026
79 of 81 checks passed
@QuantumExplorer
QuantumExplorer deleted the release_5.0.0 branch October 26, 2026 19:14
@shumkov shumkov mentioned this pull request Oct 27, 2026
14 of 21 tasks
thepastaclaw pushed a commit to thepastaclaw/platform that referenced this pull request Nov 2, 2026
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>
@coderabbitai coderabbitai Bot mentioned this pull request Nov 4, 2026
13 of 22 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

waiting-self-review Waiting for the author to post /self-reviewed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants