chore(release): update changelog and version to 3.0.0-dev.5#2927
chore(release): update changelog and version to 3.0.0-dev.5#2927
Conversation
WalkthroughDevelopment version bump from 3.0.0-dev.4 to 3.0.0-dev.5 across the entire monorepo. Updates root-level Cargo.toml and package.json, appends changelog entries, and increments version fields in approximately 25 package.json manifest files. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested reviewers
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Actionable comments posted: 2
📜 Review details
Configuration used: defaults
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
Cargo.lockis excluded by!**/*.lock
📒 Files selected for processing (26)
CHANGELOG.mdCargo.tomlpackage.jsonpackages/bench-suite/package.jsonpackages/dapi-grpc/package.jsonpackages/dapi/package.jsonpackages/dash-spv/package.jsonpackages/dashmate/package.jsonpackages/dashpay-contract/package.jsonpackages/dpns-contract/package.jsonpackages/feature-flags-contract/package.jsonpackages/js-dapi-client/package.jsonpackages/js-dash-sdk/package.jsonpackages/js-evo-sdk/package.jsonpackages/js-grpc-common/package.jsonpackages/keyword-search-contract/package.jsonpackages/masternode-reward-shares-contract/package.jsonpackages/platform-test-suite/package.jsonpackages/token-history-contract/package.jsonpackages/wallet-lib/package.jsonpackages/wallet-utils-contract/package.jsonpackages/wasm-dpp/package.jsonpackages/wasm-dpp2/package.jsonpackages/wasm-drive-verify/package.jsonpackages/wasm-sdk/package.jsonpackages/withdrawals-contract/package.json
🧰 Additional context used
🧠 Learnings (21)
📓 Common learnings
Learnt from: QuantumExplorer
Repo: dashpay/platform PR: 2431
File: packages/rs-drive/Cargo.toml:55-60
Timestamp: 2025-01-19T07:36:46.042Z
Learning: The grovedb dependencies in packages/rs-drive/Cargo.toml and related files are intentionally kept at specific revisions rather than using the latest stable version, with plans to update them at a later time.
📚 Learning: 2024-10-09T00:22:57.778Z
Learnt from: shumkov
Repo: dashpay/platform PR: 2206
File: packages/rs-platform-version/src/version/protocol_version.rs:155-157
Timestamp: 2024-10-09T00:22:57.778Z
Learning: In the dashmate default configurations, the default protocol version for local networks has been removed, and an update mechanism for the protocol version in the consensus parameters has been implemented.
Applied to files:
packages/dashmate/package.json
📚 Learning: 2025-10-15T14:45:30.856Z
Learnt from: lklimek
Repo: dashpay/platform PR: 2716
File: packages/dashmate/src/test/constants/services.js:4-4
Timestamp: 2025-10-15T14:45:30.856Z
Learning: In the dashmate codebase (packages/dashmate), during the DAPI Rust migration (rs-dapi), the old service keys `dapi_api` and `dapi_core_streams` are intentionally kept in `generateEnvsFactory.js` for backward compatibility even though the test constants in `src/test/constants/services.js` have been updated to use `rs_dapi`. These deprecated keys will be removed in a future PR after the transition is complete.
Applied to files:
packages/dashmate/package.jsonpackages/dapi/package.json
📚 Learning: 2025-09-22T05:59:31.140Z
Learnt from: shumkov
Repo: dashpay/platform PR: 2783
File: packages/js-evo-sdk/tests/functional/dpns.spec.mjs:2-2
Timestamp: 2025-09-22T05:59:31.140Z
Learning: The dist/evo-sdk.module.js file in packages/js-evo-sdk is a generated build artifact created during the build process, not a source file that should exist in the repository.
Applied to files:
packages/js-evo-sdk/package.json
📚 Learning: 2025-11-25T13:10:23.481Z
Learnt from: CR
Repo: dashpay/platform PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-11-25T13:10:23.481Z
Learning: Use JavaScript/TypeScript for client SDKs, developer tools, and test suite
Applied to files:
packages/js-evo-sdk/package.jsonpackages/wasm-sdk/package.json
📚 Learning: 2025-10-23T13:04:39.160Z
Learnt from: thephez
Repo: dashpay/platform PR: 2816
File: packages/js-dapi-client/lib/networkConfigs.js:17-40
Timestamp: 2025-10-23T13:04:39.160Z
Learning: For the testnet DAPI address whitelist in packages/js-dapi-client/lib/networkConfigs.js, nodes may be intentionally excluded even if they are ENABLED if they are running pre-2.1 versions. Version compatibility is an important filtering criterion beyond just enabled status.
Applied to files:
packages/dapi/package.json
📚 Learning: 2025-10-29T11:37:57.299Z
Learnt from: lklimek
Repo: dashpay/platform PR: 2818
File: packages/dashmate/test/unit/templates/dynamicCompose.spec.js:1-4
Timestamp: 2025-10-29T11:37:57.299Z
Learning: In the dashpay/platform repository's dashmate package (packages/dashmate), test files do not need to import `expect` from chai because test/bootstrap.js sets it up globally with `global.expect = expect;`. The bootstrap file is automatically loaded by Mocha.
Applied to files:
packages/platform-test-suite/package.json
📚 Learning: 2025-07-10T00:37:09.586Z
Learnt from: QuantumExplorer
Repo: dashpay/platform PR: 2690
File: packages/wasm-sdk/src/queries/document.rs:383-384
Timestamp: 2025-07-10T00:37:09.586Z
Learning: In the Dash platform, DPNS (Dash Platform Name Service) contracts have the same ID across all networks (mainnet, testnet, etc.), so hardcoding the DPNS contract ID is appropriate and doesn't need to be configurable.
Applied to files:
packages/dpns-contract/package.json
📚 Learning: 2024-10-17T08:52:54.300Z
Learnt from: shumkov
Repo: dashpay/platform PR: 2248
File: packages/rs-drive-abci/src/main.rs:106-111
Timestamp: 2024-10-17T08:52:54.300Z
Learning: In this project, the environment variable `CARGO_PKG_RUST_VERSION` is defined and can be used safely with the `env!` macro.
Applied to files:
Cargo.toml
📚 Learning: 2025-11-25T13:10:23.481Z
Learnt from: CR
Repo: dashpay/platform PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-11-25T13:10:23.481Z
Learning: Run Rust tests for packages using `cargo test -p <package_name>` and all Rust tests with `cargo test --workspace`
Applied to files:
Cargo.toml
📚 Learning: 2024-10-18T15:39:51.172Z
Learnt from: lklimek
Repo: dashpay/platform PR: 2254
File: packages/rs-sdk/src/sdk.rs:585-585
Timestamp: 2024-10-18T15:39:51.172Z
Learning: The 'platform' project uses Rust version 1.80, so code in 'packages/rs-sdk' can use features available in Rust 1.80, such as the `abs_diff()` method.
Applied to files:
Cargo.toml
📚 Learning: 2025-01-19T07:36:46.042Z
Learnt from: QuantumExplorer
Repo: dashpay/platform PR: 2431
File: packages/rs-drive/Cargo.toml:55-60
Timestamp: 2025-01-19T07:36:46.042Z
Learning: The grovedb dependencies in packages/rs-drive/Cargo.toml and related files are intentionally kept at specific revisions rather than using the latest stable version, with plans to update them at a later time.
Applied to files:
Cargo.toml
📚 Learning: 2025-10-09T16:00:42.724Z
Learnt from: lklimek
Repo: dashpay/platform PR: 2716
File: packages/rs-dash-event-bus/Cargo.toml:4-4
Timestamp: 2025-10-09T16:00:42.724Z
Learning: Rust edition 2024 was released and stabilized in Rust 1.85 on February 20, 2025. Using `edition = "2024"` in Cargo.toml is valid and supported.
Applied to files:
Cargo.toml
📚 Learning: 2025-03-11T09:39:23.071Z
Learnt from: shumkov
Repo: dashpay/platform PR: 2489
File: packages/rs-dpp/Cargo.toml:32-32
Timestamp: 2025-03-11T09:39:23.071Z
Learning: In the Dash Platform project, dependencies are currently managed using Git repository references with tags (repo+tag format in Cargo.toml) rather than published crates, as the team is not currently publishing crates to crates.io.
Applied to files:
packages/js-dash-sdk/package.json
📚 Learning: 2025-09-03T14:42:29.958Z
Learnt from: thephez
Repo: dashpay/platform PR: 2754
File: packages/wasm-sdk/docs.html:1970-1971
Timestamp: 2025-09-03T14:42:29.958Z
Learning: In packages/wasm-sdk/, the docs.html file is auto-generated from api-definitions.json. Any documentation fixes should be made in api-definitions.json rather than directly in docs.html, as manual changes to docs.html would be overwritten during regeneration.
Applied to files:
packages/wasm-dpp/package.jsonpackages/wasm-sdk/package.jsonpackages/wasm-dpp2/package.jsonpackages/wasm-drive-verify/package.json
📚 Learning: 2025-09-03T14:41:16.196Z
Learnt from: thephez
Repo: dashpay/platform PR: 2754
File: packages/wasm-sdk/AI_REFERENCE.md:766-766
Timestamp: 2025-09-03T14:41:16.196Z
Learning: In packages/wasm-sdk/, the AI_REFERENCE.md file is auto-generated from api-definitions.json. Any documentation fixes should be made in api-definitions.json rather than directly in AI_REFERENCE.md, as manual changes to AI_REFERENCE.md would be overwritten during regeneration.
Applied to files:
packages/wasm-sdk/package.jsonpackages/wasm-dpp2/package.jsonpackages/wasm-drive-verify/package.json
📚 Learning: 2025-07-28T20:00:08.502Z
Learnt from: QuantumExplorer
Repo: dashpay/platform PR: 2711
File: packages/wasm-sdk/AI_REFERENCE.md:771-783
Timestamp: 2025-07-28T20:00:08.502Z
Learning: In packages/wasm-sdk/AI_REFERENCE.md, the documentation correctly shows the actual SDK method signatures (including identityCreate and identityTopUp with their full parameter lists), which may differ from the UI inputs shown in fixed_definitions.json. The UI may collect fewer parameters from users while handling additional requirements internally.
Applied to files:
packages/wasm-sdk/package.json
📚 Learning: 2025-09-02T13:30:17.703Z
Learnt from: thephez
Repo: dashpay/platform PR: 2739
File: packages/wasm-sdk/test/ui-automation/tests/state-transitions.spec.js:1-171
Timestamp: 2025-09-02T13:30:17.703Z
Learning: In packages/wasm-sdk/index.html, state transition definitions are loaded dynamically from api-definitions.json via the loadApiDefinitions() function that fetches './api-definitions.json'. The UI doesn't have hardcoded transition definitions - instead it populates categories, types, inputs, and labels from this JSON configuration file at runtime.
Applied to files:
packages/wasm-sdk/package.json
📚 Learning: 2025-11-25T13:10:23.481Z
Learnt from: CR
Repo: dashpay/platform PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-11-25T13:10:23.481Z
Learning: Keep WASM SDK documentation in sync by running `python3 generate_docs.py` after changes to packages/wasm-sdk
Applied to files:
packages/wasm-sdk/package.json
📚 Learning: 2025-09-02T13:30:17.703Z
Learnt from: thephez
Repo: dashpay/platform PR: 2739
File: packages/wasm-sdk/test/ui-automation/tests/state-transitions.spec.js:1-171
Timestamp: 2025-09-02T13:30:17.703Z
Learning: In packages/wasm-sdk/index.html, state transition definitions are loaded dynamically from api-definitions.json rather than being hardcoded in the HTML file. The UI loads transition categories, types, inputs, and labels from this JSON configuration file.
Applied to files:
packages/wasm-sdk/package.json
📚 Learning: 2025-09-03T19:33:21.688Z
Learnt from: thephez
Repo: dashpay/platform PR: 2754
File: packages/wasm-sdk/api-definitions.json:1285-1285
Timestamp: 2025-09-03T19:33:21.688Z
Learning: In packages/wasm-sdk/api-definitions.json, thephez prefers to keep the existing "ripemd160hash20bytes1234" placeholder for ECDSA_HASH160 data field in documentation examples rather than using a valid base64-encoded format, maintaining consistency with the previous documentation approach.
Applied to files:
packages/wasm-sdk/package.json
🔇 Additional comments (24)
packages/dashpay-contract/package.json (1)
3-3: Version bump applied correctly.The package version has been updated to 3.0.0-dev.5 as expected for this release.
packages/wasm-dpp/package.json (1)
3-3: Version bump applied correctly.The package version has been updated to 3.0.0-dev.5 as expected for this release.
packages/js-evo-sdk/package.json (1)
3-3: Version bump applied correctly.The package version has been updated to 3.0.0-dev.5 as expected for this release.
packages/feature-flags-contract/package.json (1)
3-3: Version bump applied correctly.The package version has been updated to 3.0.0-dev.5 as expected for this release.
packages/js-dash-sdk/package.json (1)
3-3: Version bump applied correctly.The package version has been updated to 6.0.0-dev.5 as expected for this release.
packages/wasm-sdk/package.json (1)
3-3: Version bump applied correctly.The package version has been updated to 3.0.0-dev.5 as expected for this release.
packages/wasm-drive-verify/package.json (1)
6-6: Version bump applied correctly.The package version has been updated to 3.0.0-dev.5 as expected for this release.
package.json (1)
3-3: Version bump applied correctly.The root package version has been updated to 3.0.0-dev.5 as expected for this release.
packages/keyword-search-contract/package.json (1)
3-3: LGTM! Version bump is correct.The version update from 3.0.0-dev.4 to 3.0.0-dev.5 aligns with the release chore objectives.
Cargo.toml (1)
48-48: LGTM! Workspace version bump is correct.The version update to 3.0.0-dev.5 properly synchronizes the Rust workspace version with the JavaScript package versions across the monorepo.
packages/js-grpc-common/package.json (1)
3-3: LGTM! Version bump is consistent.packages/withdrawals-contract/package.json (1)
3-3: LGTM! Version bump is consistent.packages/wasm-dpp2/package.json (1)
3-3: LGTM! Version bump is consistent.packages/platform-test-suite/package.json (1)
4-4: LGTM! Version bump is consistent.packages/dapi-grpc/package.json (1)
3-3: LGTM! Version bump is consistent.packages/wallet-lib/package.json (1)
3-3: LGTM! Version bump is correct.The version increment from 10.0.0-dev.4 to 10.0.0-dev.5 aligns with the release chore objectives.
packages/bench-suite/package.json (1)
4-4: LGTM! Version bump is correct.The version increment from 3.0.0-dev.4 to 3.0.0-dev.5 is consistent with the monorepo-wide release.
packages/dapi/package.json (1)
4-4: LGTM! Version bump is correct.The version increment from 3.0.0-dev.4 to 3.0.0-dev.5 is consistent with the coordinated release update.
packages/masternode-reward-shares-contract/package.json (1)
3-3: LGTM! Version bump is correct.The version increment from 3.0.0-dev.4 to 3.0.0-dev.5 is consistent with the release objectives.
packages/wallet-utils-contract/package.json (1)
3-3: LGTM! Version bump is correct.The version increment from 3.0.0-dev.4 to 3.0.0-dev.5 aligns with the monorepo-wide version update.
packages/dash-spv/package.json (1)
3-3: LGTM! Version bump is correct.The version increment from 4.0.0-dev.4 to 4.0.0-dev.5 is consistent with the release chore objectives.
packages/dashmate/package.json (1)
3-3: LGTM! Version bump is correct.The version has been properly updated to 3.0.0-dev.5 as part of the release preparation.
packages/token-history-contract/package.json (1)
3-3: LGTM! Version bump is correct.The version has been properly updated to 3.0.0-dev.5 as part of the release preparation.
packages/js-dapi-client/package.json (1)
3-3: Manual verification required for version consistency across monorepoThe version bump to 3.0.0-dev.5 for packages/js-dapi-client/package.json appears appropriate, but automated verification of workspace-wide consistency could not be completed. A manual check is recommended to confirm that all interdependent packages in the monorepo have been updated to matching versions and that workspace:* dependencies will resolve correctly.
| * **drive-abci:** verify apphash in finalize_block ([#2878](undefined/undefined/undefined/issues/2878)) | ||
|
|
||
|
|
||
| ### Build System | ||
|
|
||
| * upgrade yarn to latest version ([#2926](undefined/undefined/undefined/issues/2926)) |
There was a problem hiding this comment.
Fix broken issue/PR links in new 3.0.0‑dev.5 entry
Both new bullets use undefined/undefined/undefined/issues/... in their Markdown links, which will 404 and are inconsistent with the rest of the changelog that points to https://github.com/dashpay/platform/issues/....
Consider updating them to match the existing pattern, e.g.:
Proposed link fixes
- * **drive-abci:** verify apphash in finalize_block ([#2878](undefined/undefined/undefined/issues/2878))
+ * **drive-abci:** verify apphash in finalize_block ([#2878](https://github.com/dashpay/platform/issues/2878))
- * upgrade yarn to latest version ([#2926](undefined/undefined/undefined/issues/2926))
+ * upgrade yarn to latest version ([#2926](https://github.com/dashpay/platform/issues/2926))📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| * **drive-abci:** verify apphash in finalize_block ([#2878](undefined/undefined/undefined/issues/2878)) | |
| ### Build System | |
| * upgrade yarn to latest version ([#2926](undefined/undefined/undefined/issues/2926)) | |
| * **drive-abci:** verify apphash in finalize_block ([#2878](https://github.com/dashpay/platform/issues/2878)) | |
| ### Build System | |
| * upgrade yarn to latest version ([#2926](https://github.com/dashpay/platform/issues/2926)) |
🤖 Prompt for AI Agents
In CHANGELOG.md around lines 6 to 11, the two issue/PR links use malformed paths
like `undefined/undefined/undefined/issues/...` which will 404; replace those
with the canonical GitHub issue/PR URLs (e.g.
`https://github.com/dashpay/platform/issues/2878` and
`https://github.com/dashpay/platform/issues/2926`) so the markdown links match
the rest of the changelog and point to the correct issue numbers.
| { | ||
| "name": "@dashevo/dpns-contract", | ||
| "version": "3.0.0-dev.4", | ||
| "version": "3.0.0-dev.5", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Verify all package.json and Cargo.toml files have consistent version 3.0.0-dev.5
echo "=== Checking package.json files for version consistency ==="
fd -e json package.json -x jq -r '.name + ": " + (.version // "missing")' {} \; | sort
echo -e "\n=== Checking Cargo.toml workspace version ==="
if [ -f "Cargo.toml" ]; then
rg -A 2 '^\[workspace\.package\]' Cargo.toml | rg 'version'
else
echo "No Cargo.toml found at root"
fiRepository: dashpay/platform
Length of output: 1038
LGTM! Version bump to 3.0.0-dev.5 is correct for dpns-contract.
Note: The monorepo has intentional version variations. While most packages are at 3.0.0-dev.5, some packages maintain different major versions: @dashevo/dash-spv (4.0.0-dev.5), @dashevo/wallet-lib (10.0.0-dev.5), and dash (6.0.0-dev.5). Cargo.toml workspace version is correctly set to 3.0.0-dev.5.
🤖 Prompt for AI Agents
In packages/dpns-contract/package.json around lines 3 to 3, the version is set
to "3.0.0-dev.5" which is correct per the review; no changes are required—leave
the version as-is and ensure it remains consistent with the Cargo.toml workspace
and intentional monorepo version variations.
Issue being fixed or feature implemented
What was done?
How Has This Been Tested?
Breaking Changes
Checklist:
For repository code-owners and collaborators only
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.