chore(release): update changelog and bump version to 4.2.0-beta.6

[QuantumExplorer]

Basic explanation

Cuts the 4.2.0-beta.6 prerelease: every package and crate moves to version 4.2.0-beta.6 and CHANGELOG.md gains the beta.6 section (71 commits since v4.2.0-beta.5). No code changes. After merge, publishing the GitHub release builds and ships the artifacts.

Issue being fixed or feature implemented

Release new Dash Platform version

What was done?

• Updated changelog
• Bumped packages version (root, all npm packages, Cargo workspace, Cargo.lock)
• Restored offset majors with yarn constraints --fix: dash-spv 5.2.0-beta.6, dash 7.2.0-beta.6, wallet-lib 11.2.0-beta.6
• Changelog base: v4.2.0-beta.5
• No new publishable npm packages since beta.5, so no npm trusted publisher needs configuring before the release

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

🤖 Generated with Claude Code

PR Hygiene · 1b2d782

• Bots — coderabbitai not yet · thepastaclaw not yet — /skip-bots proceeds without the ones not yet reported
• Self-review — post /self-reviewed once the bots are done
• Within your 5 open PRs — this one is beyond the limit; it waits until one merges
• 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 box is checked the PR Hygiene check passes and this can merge.

[coderabbitai]

Warning

Review limit reached

Next included review available in 17 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Repository: dashpay/platform/.coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: b2238c9f-8a67-4a36-bef1-e70eb938ec48

📥 Commits

Reviewing files that changed from the base of the PR and between e776f95 and 1b2d782.

⛔ 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

---

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.}

[thepastaclaw]

🕓 Queued for automated review — 5th in line, estimated start in ~25 min (commit 1b2d782)
Estimated review time once started: ~45 min (two-phase automated review; median of recent runs).

• Request priority review — click to move this review to the front of the queue.