chore(release): update changelog and bump version to 1.4.0-dev.5

[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

Release Notes for Version 1.4.0-dev.5

• New Features

  • Introduced owner keys to identities, enhancing the verification process.
  • Added a convenience method to retrieve public key data based on key type.

• Version Updates

  • All relevant packages have been incremented from version 1.4.0-dev.4 to 1.4.0-dev.5, indicating a new development iteration.

These updates improve functionality and ensure users are aware of the latest changes across the platform.

[coderabbitai]

Walkthrough

The pull request introduces version 1.4.0-dev.5 for the Dashpay platform, updating multiple packages and their respective package.json and Cargo.toml files. Key changes include the addition of owner keys to identities, impacting the verification process, and a new method for retrieving public key data. The changelog has been structured to outline breaking changes, new features, and bug fixes across various versions, enhancing clarity on the platform's evolution.

Changes

File	Change Summary
CHANGELOG.md	Added owner keys to identities (breaking change), introduced getPublicKeyDataForPrivateKey(keyType) method.
package.json	Updated version from 1.4.0-dev.4 to 1.4.0-dev.5 across multiple packages.
Cargo.toml	Updated version from 1.4.0-dev.4 to 1.4.0-dev.5 across multiple packages; minor corrections in rs-drive.
packages/platform-value/Cargo.toml	Updated dependency bincode to version 2.0.0-rc.3 with feature serde.

Possibly related PRs

• feat(platform)!: add owner keys to identities, fixed verification of use of owner keys #2215: This PR introduces owner keys to identities and modifies the verification process for their use, which directly relates to the changes made in the main PR regarding the addition of owner keys to identities and the associated breaking changes.

Poem

In the land of Dashpay, changes abound,
With owner keys added, new features are found.
Version bumps dance, like rabbits in play,
Enhancing the platform, come join the fray!
With each little tweak, our progress is clear,
Hopping towards greatness, we have nothing to fear! 🐰✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (2)

CHANGELOG.md (2)

Line range hint 13-24: Consider adding more details to the breaking changes description.

While the breaking changes are listed, it might be helpful to provide more context or explanation for each change. For example, for the change "add owner keys to identities, fixed verification of use of owner keys", it would be beneficial to briefly explain the impact of this change on existing systems or how users might need to adapt.

---

Line range hint 3397-3411: Consider updating the "Previous versions" section.

The "Previous versions" section at the end of the file refers to versions before 0.21.x and links to separate changelogs. Given that this changelog now includes versions up to 1.4.0-dev.5, it might be worth updating this section or considering if it's still necessary to keep.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 75fbac8 and d3ca0fe.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (43)

• CHANGELOG.md (1 hunks)
• 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/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/wallet-lib/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)

✅ Files skipped from review due to trivial changes (42)

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

🧰 Additional context used

🔇 Additional comments (2)

CHANGELOG.md (2)

1-11: LGTM: Recent changelog entry is well-structured and informative.

The changelog entry for version 1.4.0-dev.5 is well-formatted and provides clear information about the changes. It includes the version number, date, and a link to compare with the previous version. The changes are properly categorized into "BREAKING CHANGES" and "Features".

---

Line range hint 26-3395: LGTM: Comprehensive changelog with good historical information.

The changelog provides a detailed history of changes across multiple versions, which is very useful for users and developers. The consistent use of categories (Features, Bug Fixes, Breaking Changes, etc.) makes it easy to understand the nature of each change.