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.1 #2391

Merged
merged 2 commits into from
Dec 17, 2024

Conversation

shumkov
Copy link
Member

@shumkov shumkov commented Dec 16, 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

    • Updated version to 1.8.0-dev.1 across multiple packages, indicating a shift to development versions.
    • Addressed a security vulnerability in the system.
    • Introduced a new migration function for version '1.8.0' to update Docker images for specific components.
  • Bug Fixes

    • Corrected a typo in the package description for withdrawals-contract.
  • Chores

    • Removed deprecated scripts and updated various dependencies to ensure compatibility.
  • Tests

    • Enhanced test coverage with new test vectors generated using the testnet.
  • Breaking Changes

    • Noted significant modifications to SDK and platform functionalities in the changelog.

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

coderabbitai bot commented Dec 16, 2024

Walkthrough

This pull request introduces version 1.8.0-dev.1 across multiple packages in the Dash ecosystem. The changes primarily involve version updates, dependency modifications, and minor administrative adjustments. Key updates include incrementing package versions, updating dependencies like bincode and dashcore-rpc, and making small corrections in package metadata. The modifications span JavaScript and Rust packages, indicating a coordinated versioning effort across the project's different components.

Changes

File Change Summary
CHANGELOG.md Added version [1.8.0-dev.1] with updates to CI, protocol version, and dependencies
package.json and various Cargo.toml files Version bumped from 1.7.0 to 1.8.0-dev.1 across multiple packages
Dependency Updates Updated bincode to 2.0.0-rc.3, dashcore-rpc to v0.15.13, and other minor dependency modifications
packages/dashmate/configs/getConfigFileMigrationsFactory.js Added migration function for version 1.8.0 to update Docker images

Possibly Related PRs

Suggested Labels

dashmate, cleanup

Suggested Reviewers

  • QuantumExplorer
  • lklimek

Poem

🐰 Versioning Hop! 🐰
From one-point-seven to dev,
Packages dance with a rev,
Bincode twirls, dependencies sway,
A version update's playful display!
CodeRabbit's magic makes versions gleam 🌟

Tip

CodeRabbit's docstrings feature is now available as part of our Early Access Program! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request. We would love to hear your feedback on Discord.


📜 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 ed02a91 and 5762f38.

📒 Files selected for processing (1)
  • packages/dashmate/configs/getConfigFileMigrationsFactory.js (1 hunks)
🔇 Additional comments (1)
packages/dashmate/configs/getConfigFileMigrationsFactory.js (1)

1059-1066: LGTM! Version migration function follows established patterns.

The new migration function for version 1.8.0 correctly updates the Docker images for platform components, maintaining consistency with other development version migrations.

Let's verify the version consistency across the codebase:

✅ Verification successful

Version consistency verified across package files and Docker images

The verification confirms:

  • All package.json files consistently use version "1.8.0-dev.1"
  • Docker image tags 'dashpay/drive:1-dev' and 'dashpay/dapi:1-dev' are consistently used in the configuration migrations
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify version consistency across package files
# Test: Search for version numbers in package.json files
# Expect: Consistent version numbers (1.8.0-dev.1)

# Check package.json files for version
rg -g "package.json" '"version":\s*"1\.8\.0.*"'

# Check Docker image tags in configuration files
rg -g "*.js" 'dashpay/(drive|dapi):1-dev'

Length of output: 2423


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 generate docstrings to generate docstrings for this PR. (Beta)
  • @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.

lklimek
lklimek previously approved these changes Dec 16, 2024
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: 0

🔭 Outside diff range comments (1)
packages/rs-platform-value/Cargo.toml (1)

Custom ciborium fork requires attention - last update over a year ago

The fork's feat-ser-null-as-undefined branch shows concerning signs:

  • Last commit was on December 30, 2022 (over a year ago)
  • The fork is used across multiple packages in the codebase
  • No documentation found explaining the fork's maintenance strategy

Consider:

  • Evaluating if the custom serialization feature is still needed
  • Creating an issue in the official ciborium repository to propose the feature
  • If the feature is essential, consider maintaining it internally or finding alternative solutions
🔗 Analysis chain

Line range hint 12-12: Verify custom ciborium fork stability

Using a custom fork of ciborium with a feature branch could introduce stability risks. Please ensure:

  1. The fork is actively maintained
  2. There's a plan to migrate back to the official repository
  3. The feature branch is stable

Let me gather more information about the fork's activity and stability.


Let me try a different approach to check the fork's activity.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if the ciborium dependency is used consistently across the codebase
rg -g 'Cargo.toml' 'ciborium.*qrayven'

Length of output: 734


Script:

#!/bin/bash
# Check the fork's activity and the specific branch
gh api repos/qrayven/ciborium/branches/feat-ser-null-as-undefined --jq '.commit.commit.author.date, .commit.sha'

# Check recent commits on the branch
gh api repos/qrayven/ciborium/commits --query branch=feat-ser-null-as-undefined --jq '.[0:3] | .[] | {date: .commit.author.date, message: .commit.message}'

Length of output: 1700


Script:

#!/bin/bash
# Check the last commit date and message on the specific branch
gh api repos/qrayven/ciborium/commits/feat-ser-null-as-undefined --jq '.commit.author.date, .commit.message'

# Check if there's a README or documentation about this fork's purpose
rg -g '*.md' -i 'ciborium.*qrayven|feat-ser-null-as-undefined' --type-add 'md:*.md'

Length of output: 281

🧹 Nitpick comments (3)
packages/rs-sdk/Cargo.toml (1)

Line range hint 42-43: Address TODO and avoid using develop branch

Two concerns in the dependencies:

  1. TODO comment indicates dashcore-rpc should be removed once correct core rpc implementation is available
  2. bip37-bloom-filter is using the develop branch, which can be unstable

Consider:

  1. Creating a tracking issue for the TODO
  2. Pinning bip37-bloom-filter to a specific commit or tag

Would you like me to create a tracking issue for implementing the correct core rpc implementation?

CHANGELOG.md (2)

1-24: LGTM! Consider adding breaking changes section if applicable.

The changelog follows the conventional format and provides good categorization of changes. The latest version 1.8.0-dev.1 includes CI, test and chore updates.

Consider explicitly adding a "BREAKING CHANGES" section for version 1.8.0-dev.1 if there are any breaking changes, even if minor, to help users prepare for the upgrade.


Line range hint 1-2500: Consider standardizing the changelog format across all versions.

While the overall structure is good, there are some minor format inconsistencies in older entries. For better readability and maintenance:

  1. Use consistent section ordering across versions (e.g., Breaking Changes, Features, Bug Fixes, etc.)
  2. Maintain consistent indentation for sub-bullets
  3. Use consistent formatting for version links
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 494054a and ed02a91.

⛔ Files ignored due to path filters (1)
  • Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (45)
  • 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/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)
✅ Files skipped from review due to trivial changes (37)
  • packages/check-features/Cargo.toml
  • packages/dashpay-contract/Cargo.toml
  • packages/masternode-reward-shares-contract/Cargo.toml
  • packages/wallet-utils-contract/Cargo.toml
  • packages/withdrawals-contract/package.json
  • packages/wallet-lib/package.json
  • packages/feature-flags-contract/Cargo.toml
  • packages/rs-platform-versioning/Cargo.toml
  • packages/dpns-contract/package.json
  • packages/js-dapi-client/package.json
  • packages/dash-spv/package.json
  • packages/rs-platform-value-convertible/Cargo.toml
  • packages/dpns-contract/Cargo.toml
  • packages/feature-flags-contract/package.json
  • packages/rs-platform-serialization-derive/Cargo.toml
  • packages/wallet-utils-contract/package.json
  • packages/data-contracts/Cargo.toml
  • packages/dashpay-contract/package.json
  • packages/js-grpc-common/package.json
  • packages/rs-platform-serialization/Cargo.toml
  • packages/dapi/package.json
  • packages/rs-dapi-client/Cargo.toml
  • packages/js-dash-sdk/package.json
  • packages/wasm-dpp/package.json
  • packages/dapi-grpc/package.json
  • packages/rs-dapi-grpc-macros/Cargo.toml
  • package.json
  • packages/withdrawals-contract/Cargo.toml
  • packages/masternode-reward-shares-contract/package.json
  • packages/wasm-dpp/Cargo.toml
  • packages/platform-test-suite/package.json
  • packages/rs-json-schema-compatibility-validator/Cargo.toml
  • packages/rs-drive/Cargo.toml
  • packages/dashmate/package.json
  • packages/dapi-grpc/Cargo.toml
  • packages/bench-suite/package.json
  • packages/simple-signer/Cargo.toml
🧰 Additional context used
📓 Learnings (1)
packages/rs-drive-abci/Cargo.toml (1)
Learnt from: shumkov
PR: dashpay/platform#2375
File: packages/rs-drive-abci/Cargo.toml:61-63
Timestamp: 2024-12-05T09:29:38.918Z
Learning: In the `drive-abci` package, avoid adding unused dependencies like `hashbrown` to `Cargo.toml`. The team relies on CI to detect dependency version issues.
🔇 Additional comments (12)
packages/rs-dpp/Cargo.toml (2)

3-3: LGTM: Version bump follows semantic versioning

The version bump to 1.8.0-dev.1 follows semantic versioning format and aligns with the PR objectives for a coordinated version bump across packages.


Line range hint 1-324: Verify dependency compatibility and stability

Some dependencies require attention:

  1. bincode 2.0.0-rc.3: Being a release candidate of a major version bump, it might contain breaking changes.
  2. jsonschema: Using a specific branch instead of a version could lead to instability.

Let's verify the dependencies:

✅ Verification successful

Dependencies appear stable with manageable risks

Based on the verification results:

  1. bincode 2.0.0-rc.3: No open issues labeled as breaking changes were found in the repository, suggesting the release candidate is relatively stable.

  2. jsonschema fork (configure_regexp branch):

    • Branch is actively maintained with recent commits
    • Last commit from May 2024 shows regular maintenance
    • Branch is owned and maintained by the same team (dashpay organization)

The dependencies show no immediate red flags that would warrant changes. The use of a custom branch for jsonschema is justified as it's maintained within the same organization.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for potential breaking changes in dependencies

# Check if bincode 2.0.0-rc.3 has known issues
echo "Checking bincode issues..."
gh api graphql -f query='
{
  repository(owner: "bincode-org", name: "bincode") {
    issues(states: OPEN, labels: ["breaking-change"], first: 5) {
      nodes {
        title
        url
        labels(first: 5) {
          nodes {
            name
          }
        }
      }
    }
  }
}
'

# Check if the jsonschema branch is actively maintained
echo "Checking jsonschema branch status..."
gh api repos/dashpay/jsonschema-rs/branches/configure_regexp

Length of output: 4264

packages/rs-platform-version/Cargo.toml (1)

5-5: LGTM: Version bump follows semver

The version update to 1.8.0-dev.1 follows semantic versioning conventions and aligns with the PR objectives.

packages/rs-platform-value/Cargo.toml (2)

5-5: LGTM: Version bump is consistent

The version update to 1.8.0-dev.1 is consistent with other packages in the PR.


Line range hint 11-11: Verify bincode RC version compatibility

The update to bincode 2.0.0-rc.3 is a release candidate version change. While minor, RC versions can introduce breaking changes.

✅ Verification successful

Based on the search results, I can see that bincode is extensively used throughout the codebase for serialization and deserialization. The usage appears to be consistent with version 2.0.0-rc.3 features, including:

  1. Standard configuration with big endian encoding
  2. Proper error handling for encode/decode operations
  3. Correct usage of bincode traits and derive macros
  4. No deprecated API usage

Let me verify the changelog and compatibility notes for bincode 2.0.0-rc.3.


Let me check the specific issue #885 mentioned in the changelog to understand if it's still relevant.


Based on the comprehensive analysis of the codebase:

The bincode 2.0.0-rc.3 update appears safe to use

The codebase shows proper implementation of bincode serialization/deserialization, and while there was a historical issue with identifier deserialization (#885), the current implementation in rs-platform-value/src/types/identifier.rs shows it has been properly addressed with correct decode implementation. The extensive usage across the codebase follows consistent patterns that align with bincode 2.0.0-rc.3's API.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for any bincode-related issues or compatibility problems in the codebase
rg -g '*.rs' -A 3 'bincode::'

Length of output: 74724


Script:

#!/bin/bash
# Check if there are any bincode version compatibility issues reported in commit messages or PRs
rg -g '!target' -i "bincode.*breaking|bincode.*compatibility|bincode.*issue"

Length of output: 450


Script:

#!/bin/bash
# Check the identifier deserialization implementation and recent changes
rg -g '*.rs' "impl.*Decode.*for.*Identifier|impl.*bincode::.*for.*Identifier" -A 5

Length of output: 719

packages/strategy-tests/Cargo.toml (1)

3-3: LGTM: Version and dependency updates are consistent

The version bump to 1.8.0-dev.1 and bincode update to 2.0.0-rc.3 are consistent with other packages in the PR.

packages/rs-drive-proof-verifier/Cargo.toml (2)

3-3: LGTM: Version bump is consistent

The version update to 1.8.0-dev.1 aligns with the PR objectives.


Line range hint 33-33: Verify bincode RC version compatibility

The update to bincode 2.0.0-rc.3 (release candidate) could potentially introduce breaking changes.

✅ Verification successful

Based on the search results, I can see that bincode is extensively used throughout the codebase for serialization/deserialization with consistent configuration patterns. The key findings are:

  1. The codebase uses bincode in a standardized way with consistent configuration:
bincode::config::standard()
    .with_big_endian()
    .with_no_limit()
  1. The update to bincode 2.0.0-rc.3 is used with proper error handling and configuration across multiple critical paths including:
  • State transitions
  • Document operations
  • Identity operations
  • Voting mechanisms
  • Platform serialization
  1. The codebase has proper error handling for bincode operations and follows consistent patterns.

Bincode RC version compatibility verified

The extensive usage of bincode across critical paths shows a consistent implementation pattern with proper error handling. The update to bincode 2.0.0-rc.3 appears safe as the codebase follows bincode's stable APIs and patterns.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if bincode is used in any critical serialization paths
rg -l "bincode::" | while read -r file; do
  echo "=== $file ==="
  rg "bincode::" "$file" -C 2
done

Length of output: 131070

packages/rs-drive-abci/Cargo.toml (2)

3-3: LGTM: Version bump is consistent

The version update to 1.8.0-dev.1 aligns with the PR objectives.


Line range hint 17-17: Verify stability of git dependencies

Multiple dependencies are sourced from git with specific branches/tags:

  • ciborium from custom branch 'feat-ser-null-as-undefined'
  • dashcore-rpc from tag v0.15.13

Consider pinning to specific commits for better reproducibility.

Also applies to: 18-18

packages/rs-sdk/Cargo.toml (1)

3-3: LGTM: Version bump is consistent

The version update to 1.8.0-dev.1 aligns with the PR objectives.

CHANGELOG.md (1)

1-10: Version numbering scheme follows semantic versioning correctly.

The changelog properly implements semantic versioning with:

  • Clear MAJOR.MINOR.PATCH structure
  • Appropriate pre-release tags (-dev, -alpha, -beta, -rc)
  • Consistent version incrementing

@shumkov shumkov merged commit 889d192 into v1.8-dev Dec 17, 2024
129 checks passed
@shumkov shumkov deleted the release_1.8.0-dev.1 branch December 17, 2024 12:26
lklimek added a commit that referenced this pull request Mar 6, 2025
commit 6776651
Author: QuantumExplorer <quantum@dash.org>
Date:   Sat Mar 1 22:23:41 2025 +0700

    chore: update to latest dash core 37 (#2483)

commit 1501103
Merge: a7c7a0f da17fc5
Author: Ivan Shumkov <ivan@shumkov.ru>
Date:   Thu Feb 27 14:21:41 2025 +0700

    chore: merge master and resolve conflicts (#2481)

commit da17fc5
Author: pshenmic <pshenmic@gmail.com>
Date:   Thu Feb 27 13:31:51 2025 +0700

    feat(js-dash-sdk): fix tests after merge

commit c7e40cb
Merge: c57e8b2 f9eb069
Author: Ivan Shumkov <ivan@shumkov.ru>
Date:   Thu Feb 27 09:35:02 2025 +0700

    Merge remote-tracking branch 'origin/chore/merge-master' into chore/merge-master

commit c57e8b2
Author: Ivan Shumkov <ivan@shumkov.ru>
Date:   Thu Feb 27 09:34:40 2025 +0700

    test(dpp): fix assertion with the same value

commit 045b6fa
Author: Ivan Shumkov <ivan@shumkov.ru>
Date:   Thu Feb 27 09:32:33 2025 +0700

    chore(dpp): remove unnecessary type conversion

commit 8160ccd
Author: Ivan Shumkov <ivan@shumkov.ru>
Date:   Thu Feb 27 09:31:32 2025 +0700

    chore: remove duplicated commented code

commit f9eb069
Merge: 05d0085 a7c7a0f
Author: pshenmic <pshenmic@gmail.com>
Date:   Wed Feb 26 20:03:00 2025 +0700

    Merge branch 'v2.0-dev' into chore/merge-master

commit a7c7a0f
Author: pshenmic <pshenmic@gmail.com>
Date:   Wed Feb 26 19:52:02 2025 +0700

    build: bump rust version to 1.85 (#2480)

commit 05d0085
Merge: bcf1785 196976c
Author: Ivan Shumkov <ivan@shumkov.ru>
Date:   Wed Feb 26 18:03:38 2025 +0700

    Merge branch 'master' into v2.0-dev

commit bcf1785
Author: lklimek <842586+lklimek@users.noreply.github.com>
Date:   Fri Feb 21 08:43:35 2025 +0100

    feat: wasm sdk build proof-of-concept (#2405)

    Co-authored-by: Ivan Shumkov <ivan@shumkov.ru>

commit 5e32426
Author: Paul DeLucia <69597248+pauldelucia@users.noreply.github.com>
Date:   Thu Feb 20 19:22:52 2025 +0700

    fix: token already paused unpaused and frozen validation (#2466)

commit 374a036
Author: Ivan Shumkov <ivan@shumkov.ru>
Date:   Thu Feb 20 17:46:57 2025 +0700

    test: fix slowdown of JS SDK unit tests (#2475)

commit 1fed09b
Author: Ivan Shumkov <ivan@shumkov.ru>
Date:   Thu Feb 20 13:46:36 2025 +0700

    fix(dpp): invalid feature flag usage (#2477)

commit 33507bb
Author: Paul DeLucia <69597248+pauldelucia@users.noreply.github.com>
Date:   Thu Feb 20 13:18:55 2025 +0700

    fix: destroy frozen funds used wrong identity and proof verification (#2467)

commit 91a9766
Author: Ivan Shumkov <ivan@shumkov.ru>
Date:   Wed Feb 19 16:57:32 2025 +0700

    feat(sdk): return state transition execution error (#2454)

commit cb915a7
Author: Ivan Shumkov <ivan@shumkov.ru>
Date:   Wed Feb 19 16:46:54 2025 +0700

    test: fix token history contract tests (#2470)

commit 04276d5
Author: Ivan Shumkov <ivan@shumkov.ru>
Date:   Tue Feb 18 21:00:05 2025 +0700

    fix: xss vulnerability in mocha (#2469)

commit 196976c
Author: pshenmic <pshenmic@gmail.com>
Date:   Fri Feb 14 18:50:08 2025 +0700

    fix(sdk)!: bigint for uint64 values (#2443)

commit 0bd29a6
Author: pshenmic <pshenmic@gmail.com>
Date:   Fri Feb 14 17:29:35 2025 +0700

    feat(dpp): extra methods for state transitions in wasm (#2462)

commit 1eae781
Author: pshenmic <pshenmic@gmail.com>
Date:   Fri Feb 14 15:29:17 2025 +0700

    chore(platform): npm audit fix (#2463)

commit ddf4e67
Author: Ivan Shumkov <ivan@shumkov.ru>
Date:   Fri Feb 14 11:28:08 2025 +0700

    test: fix `fetchProofForStateTransition` tests and warnings (#2460)

commit d88ea46
Author: Ivan Shumkov <ivan@shumkov.ru>
Date:   Fri Feb 14 09:52:53 2025 +0700

    fix(dpp): invalid imports and tests (#2459)

commit 82e4d4c
Merge: 125cfe7 4becf5f
Author: Paul DeLucia <69597248+pauldelucia@users.noreply.github.com>
Date:   Thu Feb 13 19:05:51 2025 +0700

    fix: check if token is paused on token transfers (#2458)

commit 4becf5f
Author: pauldelucia <pauldelucia2@gmail.com>
Date:   Thu Feb 13 18:34:24 2025 +0700

    add costs

commit 907971d
Merge: 9026669 125cfe7
Author: Paul DeLucia <69597248+pauldelucia@users.noreply.github.com>
Date:   Thu Feb 13 18:05:06 2025 +0700

    Merge branch 'v2.0-dev' into feat/token-paused-validation

commit 125cfe7
Merge: 91f65c6 c286ec0
Author: Ivan Shumkov <ivan@shumkov.ru>
Date:   Thu Feb 13 15:51:46 2025 +0700

    Merge branch 'v2.0-dev' into v2.0-tokens-dev

commit 9026669
Author: pauldelucia <pauldelucia2@gmail.com>
Date:   Thu Feb 13 13:41:19 2025 +0700

    feat: check if token is paused on token transfers

commit c286ec0
Author: pshenmic <pshenmic@gmail.com>
Date:   Wed Feb 12 15:41:21 2025 +0700

    feat(sdk): add option to request all keys (#2445)

commit 91f65c6
Merge: d6b40e6 1a1c50b
Author: Paul DeLucia <69597248+pauldelucia@users.noreply.github.com>
Date:   Wed Feb 12 12:04:58 2025 +0700

    fix: wrong order of parameters in UnauthorizedTokenActionError (#2456)

commit 1a1c50b
Author: pauldelucia <pauldelucia2@gmail.com>
Date:   Wed Feb 12 11:51:31 2025 +0700

    fix: wrong order of parameters in UnauthorizedTokenActionError

commit 26aff36
Author: lklimek <842586+lklimek@users.noreply.github.com>
Date:   Tue Feb 11 13:06:54 2025 +0100

    build: bump Alpine version to 3.21 (#2074)

commit 9daa195
Author: Ivan Shumkov <ivan@shumkov.ru>
Date:   Tue Feb 11 14:38:55 2025 +0700

    ci: use github-hosted arm runner for release workflow (#2452)

commit 2b1c252
Author: Paul DeLucia <69597248+pauldelucia@users.noreply.github.com>
Date:   Tue Feb 4 16:40:34 2025 +0700

    fix: proof result error for credit transfers in sdk (#2451)

commit d6b40e6
Author: QuantumExplorer <quantum@dash.org>
Date:   Tue Feb 4 06:49:03 2025 +0700

    feat(platform): token distribution part two (#2450)

commit 93f7d44
Author: Ivan Shumkov <ivan@shumkov.ru>
Date:   Wed Jan 29 14:07:55 2025 +0700

    fix(dpp): invalid feature flag instructions (#2448)

commit 6d5af88
Author: QuantumExplorer <quantum@dash.org>
Date:   Mon Jan 27 16:59:39 2025 +0700

    feat(dpp): token distribution model (#2447)

commit e735313
Author: Ivan Shumkov <ivan@shumkov.ru>
Date:   Mon Jan 27 14:24:26 2025 +0700

    feat: add token transitions to SDK and DAPI (#2434)

commit 0743be2
Author: pshenmic <pshenmic@gmail.com>
Date:   Sun Jan 26 22:00:40 2025 +0700

    feat(dpp): extra methods for state transitions in wasm (#2401)

commit f609bcf
Merge: 3733f56 cbddb8d
Author: Ivan Shumkov <ivan@shumkov.ru>
Date:   Fri Jan 24 18:16:38 2025 +0700

    Merge branch 'v2.0-dev' into v2.0-tokens-dev

commit cbddb8d
Author: QuantumExplorer <quantum@dash.org>
Date:   Fri Jan 24 17:59:16 2025 +0700

    chore(platform): make bls sig compatibility an optional feature (#2440)

    Co-authored-by: Ivan Shumkov <ivan@shumkov.ru>

commit 764684b
Author: Ivan Shumkov <ivan@shumkov.ru>
Date:   Fri Jan 24 17:57:27 2025 +0700

    chore: ignore deprecated `lodash.get` (#2441)

commit 3733f56
Author: QuantumExplorer <quantum@dash.org>
Date:   Thu Jan 23 09:16:12 2025 +0700

    feat(platform)!: enhance token configuration and validation mechanisms (#2439)

commit 2480ceb
Author: QuantumExplorer <quantum@dash.org>
Date:   Wed Jan 22 16:33:13 2025 +0700

    chore: dapi grpc queries (#2437)

commit c9ab154
Author: QuantumExplorer <quantum@dash.org>
Date:   Wed Jan 22 15:50:25 2025 +0700

    feat(platform)!: improved token validation and token config update transition (#2435)

commit d9647cc
Author: QuantumExplorer <quantum@dash.org>
Date:   Tue Jan 21 10:28:58 2025 +0700

    feat: get proofs for tokens (#2433)

commit e5964b8
Author: QuantumExplorer <quantum@dash.org>
Date:   Mon Jan 20 23:31:50 2025 +0700

    feat: group queries (#2432)

commit 0220302
Author: QuantumExplorer <quantum@dash.org>
Date:   Sun Jan 19 14:43:51 2025 +0700

    feat(platform): proof verification for many queries and a few more queries (#2431)

commit cd1527d
Author: QuantumExplorer <quantum@dash.org>
Date:   Fri Jan 17 19:39:37 2025 +0700

    fix(dpp)!: wrapping overflow issue (#2430)

commit fd7ee85
Merge: d7143cc e4e156c
Author: Ivan Shumkov <ivan@shumkov.ru>
Date:   Thu Jan 16 21:45:47 2025 +0700

    Merge branch 'master' into v1.9-dev

commit e4e156c
Author: QuantumExplorer <quantum@dash.org>
Date:   Thu Jan 16 18:11:57 2025 +0700

    chore(release): update change log and release v1.8.0 (#2427)

    Co-authored-by: Ivan Shumkov <ivan@shumkov.ru>

commit 55a1e03
Author: QuantumExplorer <quantum@dash.org>
Date:   Thu Jan 16 15:30:42 2025 +0700

    feat(platform)!: token base support (#2383)

commit 59bf0af
Author: QuantumExplorer <quantum@dash.org>
Date:   Thu Jan 16 13:10:39 2025 +0700

    chore(release): bump to v1.8.0-rc.2 (#2426)

commit 410eb09
Author: QuantumExplorer <quantum@dash.org>
Date:   Thu Jan 16 06:31:26 2025 +0700

    fix(drive-abci): rebroadcasting should not only take first 2 quorums too (#2425)

commit 2abce8e
Author: Ivan Shumkov <ivan@shumkov.ru>
Date:   Wed Jan 15 22:51:58 2025 +0700

    chore(release): update changelog and bump version to 1.8.0-rc.1 (#2423)

commit ad5f604
Author: Ivan Shumkov <ivan@shumkov.ru>
Date:   Wed Jan 15 22:14:13 2025 +0700

    chore: update bls library (#2424)

commit c6feb5b
Author: QuantumExplorer <quantum@dash.org>
Date:   Wed Jan 15 18:57:49 2025 +0700

    feat(platform)!: distribute prefunded specialized balances after vote (#2422)

    Co-authored-by: Ivan Shumkov <ivan@shumkov.ru>

commit 94dcbb2
Author: Ivan Shumkov <ivan@shumkov.ru>
Date:   Wed Jan 15 05:51:45 2025 +0700

    chore(drive): increase withdrawal limits to 2000 Dash per day (#2287)

commit 6a0aede
Author: Ivan Shumkov <ivan@shumkov.ru>
Date:   Tue Jan 14 21:42:59 2025 +0700

    chore: fix test suite configuration script (#2402)

commit e94b7bb
Author: QuantumExplorer <quantum@dash.org>
Date:   Tue Jan 14 19:23:46 2025 +0700

    fix(drive-abci): document purchase on mutable document from different epoch had issue (#2420)

commit 4ee57a6
Author: Ivan Shumkov <ivan@shumkov.ru>
Date:   Tue Jan 14 19:12:20 2025 +0700

    fix(drive): more than one key was returned when expecting only one result (#2421)

commit be5cd6d
Author: Ivan Shumkov <ivan@shumkov.ru>
Date:   Mon Jan 13 15:12:33 2025 +0700

    fix(sdk): failed to deserialize consensus error (#2410)

commit e07271e
Author: Ivan Shumkov <ivan@shumkov.ru>
Date:   Mon Jan 13 14:57:08 2025 +0700

    chore: resolve NPM audit warnings (#2417)

commit a809df7
Author: QuantumExplorer <quantum@dash.org>
Date:   Sun Jan 12 09:21:48 2025 +0700

    test: unify identity versioned cost coverage (#2416)

commit 6d637fe
Author: Paul DeLucia <69597248+pauldelucia@users.noreply.github.com>
Date:   Fri Dec 27 09:42:04 2024 -0500

    fix: try DriveDocumentQuery from DocumentQuery start field (#2407)

commit cfd9c4d
Author: Ivan Shumkov <ivan@shumkov.ru>
Date:   Thu Dec 19 18:30:06 2024 +0700

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

commit fecda31
Merge: 37d5732 fc7d994
Author: Ivan Shumkov <ivan@shumkov.ru>
Date:   Thu Dec 19 15:33:45 2024 +0700

    Merge branch 'master' into v1.8-dev

commit fc7d994
Author: Ivan Shumkov <ivan@shumkov.ru>
Date:   Thu Dec 19 14:40:44 2024 +0700

    chore(release): update changelog and bump version to 1.7.1 (#2403)

commit adcd3b8
Author: QuantumExplorer <quantum@dash.org>
Date:   Thu Dec 19 09:54:07 2024 +0300

    fix!: emergency hard fork to fix masternode voting (#2397)

commit 37d5732
Author: Ivan Shumkov <ivan@shumkov.ru>
Date:   Wed Dec 18 22:24:37 2024 +0700

    fix(dashmate): some group commands fail with mtime not found (#2400)

commit 01a5b7a
Author: Ivan Shumkov <ivan@shumkov.ru>
Date:   Wed Dec 18 20:44:44 2024 +0700

    refactor(dpp): using deprecated param to init wasm module (#2399)

commit c5f5878
Author: Ivan Shumkov <ivan@shumkov.ru>
Date:   Wed Dec 18 18:04:14 2024 +0700

    fix(dashmate): local network starting issues (#2394)

commit 71c41ff
Author: Ivan Shumkov <ivan@shumkov.ru>
Date:   Wed Dec 18 18:03:55 2024 +0700

    perf(dpp): reduce JS binding size by 3x (#2396)

commit 21ec393
Author: lklimek <842586+lklimek@users.noreply.github.com>
Date:   Wed Dec 18 10:47:58 2024 +0100

    build!: update rust to 1.83 - backport #2393 to v1.7 (#2398)

commit d7143cc
Author: lklimek <842586+lklimek@users.noreply.github.com>
Date:   Wed Dec 18 08:53:53 2024 +0100

    build!: optimize for x86-64-v3 cpu microarchitecture (Haswell+) (#2374)

commit d318b1c
Author: lklimek <842586+lklimek@users.noreply.github.com>
Date:   Tue Dec 17 14:56:15 2024 +0100

    build: bump wasm-bindgen to 0.2.99 (#2395)

commit 889d192
Author: Ivan Shumkov <ivan@shumkov.ru>
Date:   Tue Dec 17 19:25:58 2024 +0700

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

commit 8185d21
Author: lklimek <842586+lklimek@users.noreply.github.com>
Date:   Tue Dec 17 10:47:53 2024 +0100

    feat(sdk)!: allow setting CA cert (#1924)

commit 82a6217
Author: lklimek <842586+lklimek@users.noreply.github.com>
Date:   Tue Dec 17 02:51:18 2024 +0100

    build!: update rust to 1.83 (#2393)

commit 494054a
Author: QuantumExplorer <quantum@dash.org>
Date:   Mon Dec 16 13:47:58 2024 +0300

    refactor(platform): replace bls library (#2257)

    Co-authored-by: Lukasz Klimek <842586+lklimek@users.noreply.github.com>

commit 4c203e4
Author: lklimek <842586+lklimek@users.noreply.github.com>
Date:   Mon Dec 16 10:38:34 2024 +0100

    test(sdk): generate test vectors using testnet (#2381)

commit 0ff6b27
Author: lklimek <842586+lklimek@users.noreply.github.com>
Date:   Mon Dec 16 10:37:35 2024 +0100

    chore: remove deprecated check_network_version.sh (#2084)

commit b265bb8
Author: lklimek <842586+lklimek@users.noreply.github.com>
Date:   Fri Dec 13 13:25:40 2024 +0100

    ci: fix artifact upload issue on release build (#2389)

commit 40ae73f
Author: Ivan Shumkov <ivan@shumkov.ru>
Date:   Fri Dec 13 17:35:40 2024 +0700

    chore(release): update changelog and bump version to 1.7.0 (#2387)

commit 257e3da
Author: Ivan Shumkov <ivan@shumkov.ru>
Date:   Fri Dec 13 15:44:10 2024 +0700

    chore(dashmate)!: update Core to version 22 (#2384)

commit 19a4c6d
Author: Ivan Shumkov <ivan@shumkov.ru>
Date:   Thu Dec 12 18:30:14 2024 +0700

    chore(dashmate): set tenderdash version to 1 (#2385)

commit 0e9d4dc
Author: lklimek <842586+lklimek@users.noreply.github.com>
Date:   Thu Dec 12 11:39:35 2024 +0100

    chore: address vulnerabilty GHSA-mwcw-c2x4-8c55 (#2382)

    Co-authored-by: Ivan Shumkov <ivan@shumkov.ru>

commit bdae90c
Author: Ivan Shumkov <ivan@shumkov.ru>
Date:   Thu Dec 12 13:36:04 2024 +0700

    chore(dashmate): increase subsidy for devnet (#2353)
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