fix: update package versions to 2.0.0-rc.10

[QuantumExplorer]

Issue being fixed or feature implemented

Update all relevant packages to version 2.0.0-rc.10.

What was done?

• Updated version numbers in Cargo.toml and package.json files for multiple packages from 2.0.0-rc.9 to 2.0.0-rc.10.

How Has This Been Tested?

Versions have been updated and verified through existing tests.

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

For repository code-owners and collaborators only

• I have assigned this pull request to a milestone

Summary by CodeRabbit

• Chores
  • Updated version numbers for multiple packages to the latest release candidate. No changes to features, functionality, or public interfaces.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

All changes in this pull request update the version numbers of various package manifests (both JavaScript and Rust) from release candidate 9 to release candidate 10. No modifications to code, dependencies, scripts, or exported entities are present; only the version fields in the manifest files are incremented.

Changes

Files/Paths	Change Summary
package.json, .../bench-suite/package.json, .../dapi/package.json, .../dash-spv/package.json, .../dashmate/package.json, .../dapi-grpc/package.json, .../dashpay-contract/package.json, .../dpns-contract/package.json, .../feature-flags-contract/package.json, .../js-dapi-client/package.json, .../js-dash-sdk/package.json, .../js-grpc-common/package.json, .../keyword-search-contract/package.json, .../masternode-reward-shares-contract/package.json, .../platform-test-suite/package.json, .../token-history-contract/package.json, .../wallet-lib/package.json, .../wallet-utils-contract/package.json, .../wasm-dpp/package.json, .../withdrawals-contract/package.json	Updated the version field in package.json from rc.9 to rc.10; no other changes.
.../check-features/Cargo.toml, .../dapi-grpc/Cargo.toml, .../dashpay-contract/Cargo.toml, .../data-contracts/Cargo.toml, .../dpns-contract/Cargo.toml, .../feature-flags-contract/Cargo.toml, .../keyword-search-contract/Cargo.toml, .../masternode-reward-shares-contract/Cargo.toml, .../rs-dapi-client/Cargo.toml, .../rs-dapi-grpc-macros/Cargo.toml, .../rs-dpp/Cargo.toml, .../rs-drive-abci/Cargo.toml, .../rs-drive-proof-verifier/Cargo.toml, .../rs-drive/Cargo.toml, .../rs-json-schema-compatibility-validator/Cargo.toml, .../rs-platform-serialization-derive/Cargo.toml, .../rs-platform-serialization/Cargo.toml, .../rs-platform-value-convertible/Cargo.toml, .../rs-platform-value/Cargo.toml, .../rs-platform-version/Cargo.toml, .../rs-platform-versioning/Cargo.toml, .../rs-sdk/Cargo.toml, .../simple-signer/Cargo.toml, .../strategy-tests/Cargo.toml, .../token-history-contract/Cargo.toml, .../wallet-utils-contract/Cargo.toml, .../wasm-dpp/Cargo.toml, .../withdrawals-contract/Cargo.toml	Updated the version field in Cargo.toml from rc.9 to rc.10; no other changes.

Sequence Diagram(s)

No sequence diagrams generated, as all changes are limited to version field updates in manifest files.

Possibly related PRs

• chore: update dependencies to version 2.0.0-rc.8 #2602: Also updates package versions, performing a similar version bump for a previous release candidate.
• chore: update to rc.5 #2587: Exclusively updates package version numbers across multiple manifests, similar in nature to this PR.
• chore: update package versions to 2.0.0-rc.9 #2606: Performs version bumps across the same set of packages but to a different release candidate.

Suggested labels

cleanup

Suggested reviewers

• shumkov

Poem

A hop, a skip, a version hop—
From rc.9, we never stop!
Manifests updated, carrots in tow,
No code to change, just numbers grow.
🥕
With every bump, the Platform's bright,
Another release, another byte!

Tip

⚡️ Faster reviews with caching

• CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.

Enjoy the performance boost—your workflow just got faster.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 69376a4 and 406f839.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (48)

• package.json (1 hunks)
• packages/bench-suite/package.json (1 hunks)
• packages/check-features/Cargo.toml (1 hunks)
• packages/dapi-grpc/Cargo.toml (1 hunks)
• packages/dapi-grpc/package.json (1 hunks)
• packages/dapi/package.json (1 hunks)
• packages/dash-spv/package.json (1 hunks)
• packages/dashmate/package.json (1 hunks)
• packages/dashpay-contract/Cargo.toml (1 hunks)
• packages/dashpay-contract/package.json (1 hunks)
• packages/data-contracts/Cargo.toml (1 hunks)
• packages/dpns-contract/Cargo.toml (1 hunks)
• packages/dpns-contract/package.json (1 hunks)
• packages/feature-flags-contract/Cargo.toml (1 hunks)
• packages/feature-flags-contract/package.json (1 hunks)
• packages/js-dapi-client/package.json (1 hunks)
• packages/js-dash-sdk/package.json (1 hunks)
• packages/js-grpc-common/package.json (1 hunks)
• packages/keyword-search-contract/Cargo.toml (1 hunks)
• packages/keyword-search-contract/package.json (1 hunks)
• packages/masternode-reward-shares-contract/Cargo.toml (1 hunks)
• packages/masternode-reward-shares-contract/package.json (1 hunks)
• packages/platform-test-suite/package.json (1 hunks)
• packages/rs-dapi-client/Cargo.toml (1 hunks)
• packages/rs-dapi-grpc-macros/Cargo.toml (1 hunks)
• packages/rs-dpp/Cargo.toml (1 hunks)
• packages/rs-drive-abci/Cargo.toml (1 hunks)
• packages/rs-drive-proof-verifier/Cargo.toml (1 hunks)
• packages/rs-drive/Cargo.toml (1 hunks)
• packages/rs-json-schema-compatibility-validator/Cargo.toml (1 hunks)
• packages/rs-platform-serialization-derive/Cargo.toml (1 hunks)
• packages/rs-platform-serialization/Cargo.toml (1 hunks)
• packages/rs-platform-value-convertible/Cargo.toml (1 hunks)
• packages/rs-platform-value/Cargo.toml (1 hunks)
• packages/rs-platform-version/Cargo.toml (1 hunks)
• packages/rs-platform-versioning/Cargo.toml (1 hunks)
• packages/rs-sdk/Cargo.toml (1 hunks)
• packages/simple-signer/Cargo.toml (1 hunks)
• packages/strategy-tests/Cargo.toml (1 hunks)
• packages/token-history-contract/Cargo.toml (1 hunks)
• packages/token-history-contract/package.json (1 hunks)
• packages/wallet-lib/package.json (1 hunks)
• packages/wallet-utils-contract/Cargo.toml (1 hunks)
• packages/wallet-utils-contract/package.json (1 hunks)
• packages/wasm-dpp/Cargo.toml (1 hunks)
• packages/wasm-dpp/package.json (1 hunks)
• packages/withdrawals-contract/Cargo.toml (1 hunks)
• packages/withdrawals-contract/package.json (1 hunks)

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.