chore(release): update changelog and bump version to 3.1.0-dev.7

[shumkov]

Issue being fixed or feature implemented

Release new Dash Platform version

What was done?

• Updated changelog
• Bumped packages version

How Has This Been Tested?

None

Breaking Changes

None

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

Summary by CodeRabbit

• Chores
  • Development version release 3.1.0-dev.7 with updated package versions across all components.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 43f9daaa-ad7a-4356-b5f7-23863382405e

📥 Commits

Reviewing files that changed from the base of the PR and between e230c9e and 3ef0de6.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (25)

• CHANGELOG.md
• Cargo.toml
• 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/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/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

---

📝 Walkthrough

Walkthrough

This PR bumps the workspace and package versions from 3.1.0-dev.6 to 3.1.0-dev.7. The root Cargo.toml workspace package version, root package.json, and 21 package manifests are updated with a new CHANGELOG.md entry documenting the release.

Changes

Version Bump Release Chore

Layer / File(s)	Summary
Root manifest and changelog update CHANGELOG.md, Cargo.toml, package.json	New changelog entry for 3.1.0-dev.7 (2026-05-27) with compare link. Root workspace version in Cargo.toml and root package.json bumped from 3.1.0-dev.6 to 3.1.0-dev.7.
Package workspace version bump 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/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/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	All 21 package manifest versions incremented from dev.6 to dev.7 (3.1.0-dev.7 for most; 4.1.0-dev.7 for dash-spv, 6.1.0-dev.7 for js-dash-sdk, 10.1.0-dev.7 for wallet-lib).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• dashpay/platform#3746: Both PRs are release-only updates that bump the same version fields (e.g., Cargo.toml workspace package version and multiple package.json version entries) and add a new top changelog entry, just incrementing from 3.1.0-dev.6 to 3.1.0-dev.7.
• dashpay/platform#3708: Both PRs are release-only bumps: they update the same version fields in Cargo.toml and multiple packages/*/package.json (and add a new CHANGELOG.md entry), differing only in the target dev version number.
• dashpay/platform#3718: Both PRs are the same type of release chore: they update CHANGELOG.md and bump version fields in the same root Cargo.toml/package.json and multiple packages/*/package.json manifests (only the target version differs).

Suggested reviewers

• QuantumExplorer

Poem

🐰 A bump from six to seven shows,
Across the manifest rows it flows,
Dev versions climb with every change,
The workspace dance—a simple range,
Release notes mark the path anew! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'chore(release): update changelog and bump version to 3.1.0-dev.7' clearly and specifically summarizes the main changes: updating the changelog and bumping versions across the codebase to the new development version.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release_3.1.0-dev.7

Warning

Tools execution failed with the following error:

Failed to run tools: 13 INTERNAL: Received RST_STREAM with code 2 (Internal server error)

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[thepastaclaw]

Code Review

Mechanical release bump from 3.1.0-dev.6 to 3.1.0-dev.7: CHANGELOG header, workspace Cargo.toml, root package.json, all 22 workspace package.json files, and Cargo.lock all updated consistently. No code, consensus, or behavior changes. Both Claude and Codex correctly found no in-scope issues.

Out-of-scope follow-up suggestions (2)

These are valid observations, but they are outside this PR's scope and should be handled in separate issues or author/maintainer-requested PRs rather than blocking this review.

• Empty CHANGELOG section for dev.7 — The new ## [3.1.0-dev.7] section in CHANGELOG.md has only a header with no entries because no functional commits landed between dev.6 and dev.7. Harmless, but the release tooling could be improved to either skip cutting empty releases or annotate them as (no changes) to reduce ambiguity for changelog readers.
  • Follow-up: File a separate issue to decide whether the release script should skip empty releases or annotate them explicitly.
• CHANGELOG date for dev.7 (2026-05-27) is one day after dev.6 (2026-05-26) — dev.7 is recorded as 2026-05-27 while dev.6 and the worktree's current date are 2026-05-26. Almost certainly a UTC vs local-time artifact in the release script rather than a defect in this PR.
  • Follow-up: If reproducibility matters, file a separate issue to pin the release script to a fixed timezone (UTC) or document the timezone it uses.

[github-actions]

✅ DashSDKFFI.xcframework built for this PR.

• Workflow run: https://github.com/dashpay/platform/actions/runs/26490419282
• Artifacts: DashSDKFFI.xcframework (folder), DashSDKFFI.xcframework.zip, xc_checksum.txt

SwiftPM (host the zip at a stable URL, then use):

.binaryTarget(
  name: "DashSDKFFI",
  url: "https://your.cdn.example/DashSDKFFI.xcframework.zip",
  checksum: "85da0d4af5b3bfe36a0f1fe35b771cf610b4217af0ebc0befc523c3b2767f180"
)

Xcode manual integration:

• Download 'DashSDKFFI.xcframework' artifact from the run link above.
• Drag it into your app target (Frameworks, Libraries & Embedded Content) and set Embed & Sign.
• If using the Swift wrapper package, point its binaryTarget to the xcframework location or add the package and place the xcframework at the expected path.