Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(release): update changelog and bump version to 1.8.0-dev.2 #2404

Merged
merged 2 commits into from
Dec 19, 2024

Conversation

shumkov
Copy link
Member

@shumkov shumkov commented Dec 19, 2024

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

  • New Features

    • Performance improvements with a reduction in JavaScript binding size.
    • Updates across multiple packages to version 1.8.0-dev.2.
  • Bug Fixes

    • Resolved local network starting issues and command failures in the dashmate module.
    • Addressed issues with masternode voting.
  • Documentation

    • Updated CHANGELOG.md to reflect changes across versions.
  • Chores

    • Incremented version numbers across various packages and modules.

@shumkov shumkov added this to the v1.8.0 milestone Dec 19, 2024
Copy link
Contributor

coderabbitai bot commented Dec 19, 2024

Walkthrough

This pull request represents a comprehensive version update across multiple packages in the Dashpay platform, incrementing versions from 1.8.0-dev.1 to 1.8.0-dev.2. The changes span both JavaScript (package.json) and Rust (Cargo.toml) package manifests, affecting numerous components such as dapi, dashmate, platform-test-suite, and various contracts. The update includes breaking changes, bug fixes, performance improvements, and modifications to the changelog, reflecting a routine development iteration in preparation for the next release.

Changes

File/Path Change Summary
CHANGELOG.md Updated with details for versions 1.8.0-dev.2, 1.8.0-dev.1, and 1.7.1
packages/*/package.json Version bumped from 1.8.0-dev.1 to 1.8.0-dev.2 in multiple JS packages
packages/*/Cargo.toml Version bumped from 1.8.0-dev.1 to 1.8.0-dev.2 in multiple Rust packages
packages/rs-platform-serialization/Cargo.toml Version bump and bincode dependency updated to 2.0.0-rc.3
packages/rs-drive/Cargo.toml Version bump and author email bracket correction

Possibly related PRs

Suggested Labels

cleanup

Suggested Reviewers

  • QuantumExplorer
  • lklimek

Poem

🐰 Hop, hop, version bump we go!
Packages dancing, versions in tow
From dev point one to point two
Rust and JS, a synchronized crew
CodeRabbit's magic makes platforms grow! 🚀


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

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between a5750c9 and 0a3874a.

📒 Files selected for processing (1)
  • CHANGELOG.md (1 hunks)
🔇 Additional comments (2)
CHANGELOG.md (2)

1-29: LGTM! Well-structured changelog entry for v1.8.0-dev.2

The changelog follows conventional format and clearly documents important changes including:

  • Breaking changes affecting node upgrades and build requirements
  • Critical bug fixes for network and voting functionality
  • Notable performance improvements

17-17: Notable performance improvement: 3x reduction in JS binding size

The DPP module's JavaScript binding size has been reduced by a factor of 3, which should improve load times and memory usage.

Comment on lines +5 to +6
* On epoch 13, masternode vote state transition validation logic will be changed. Nodes which aren't upgraded to this version will halt (#2397)
* Rust 1.83 is required to build the project (#2398)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codebase verification

⚠️ Potential issue

Based on the PR description and code search results, I can now provide the final response:

Critical breaking change: Masternode vote validation fix requires node upgrade by epoch 13

The masternode voting system was broken in protocol version 6 due to incorrect nonce validation against owner identity instead of voting identity. This emergency hard fork fixes the validation by using the correct voting identity nonce starting from epoch 13. All nodes must upgrade before epoch 13 to avoid halting.

🔗 Analysis chain

Critical breaking change: Masternode vote validation changes require node upgrades

Nodes that are not upgraded to this version will halt at epoch 13 due to changes in masternode vote state transition validation logic.


Let me check the referenced PR for more details about this breaking change.


Let me check the code changes related to this breaking change.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check for any references to the breaking change in code
rg -A 5 "masternode vote state transition validation"

Length of output: 851


Script:

#!/bin/bash
# Check PR #2397 for more details about the breaking change
gh pr view 2397 --json title,body,commits

# Look for any code changes related to masternode voting validation
rg -A 5 "masternode.*vote.*validation"

Length of output: 65620


Script:

#!/bin/bash
# Look for code changes related to masternode voting validation
rg -A 5 "voting.*identity.*nonce"
rg -A 5 "owner.*identity.*nonce"

Length of output: 4259

@shumkov shumkov merged commit cfd9c4d into v1.8-dev Dec 19, 2024
129 checks passed
@shumkov shumkov deleted the release_1.8.0-dev.2 branch December 19, 2024 11:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants