Skip to content

build: bump wasm-bindgen to 0.2.100 to satisfy js-sys deps #2503

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

Merged
merged 3 commits into from
Mar 18, 2025

Conversation

lklimek
Copy link
Contributor

@lklimek lklimek commented Mar 17, 2025

Issue being fixed or feature implemented

GHA failure due to js-sys requiring wasm-bindgen =0.2.100

What was done?

Updated wasm-bindgen to 0.2.100

How Has This Been Tested?

GHA

Breaking Changes

New version of wasm-bindgen-cli required to build

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 added "!" to the title and described breaking changes in the corresponding section if my code contains any
  • I have made corresponding changes to the documentation if needed

For repository code-owners and collaborators only

  • I have assigned this pull request to a milestone

Summary by CodeRabbit

  • Chores
    • Upgraded our WebAssembly tooling and related dependencies to version 0.2.100 for improved stability.
  • Documentation
    • Revised installation instructions to reflect the updated tooling version, ensuring a more consistent setup experience.

@lklimek lklimek added this to the v2.0.0 milestone Mar 17, 2025
Copy link
Contributor

coderabbitai bot commented Mar 17, 2025

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)
  • Cargo.lock is excluded by !**/*.lock

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

This pull request updates the version of the wasm-bindgen-cli tool and the wasm-bindgen dependency from version 0.2.99 to 0.2.100 across multiple files. The change spans Dockerfiles, GitHub Actions workflows, README files, and Cargo.toml configurations. Additionally, a comma was inserted in a feature list within one Cargo.toml file for proper syntax. No alterations to control flow or error handling were introduced.

Changes

File(s) Change Summary
.devcontainer/Dockerfile, .github/workflows/release.yml, .github/workflows/tests-build-js.yml, Dockerfile, README.md, packages/wasm-dpp/README.md Updated installation commands for wasm-bindgen-cli from version 0.2.99 to 0.2.100.
packages/wasm-dpp/Cargo.toml, packages/wasm-sdk/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-platform-serialization/Cargo.toml, packages/rs-platform-value/Cargo.toml, packages/simple-signer/Cargo.toml, packages/strategy-tests/Cargo.toml Updated bincode dependency from "2.0.0-rc.3" to "=2.0.0-rc.3" for exact version matching; added commas for proper syntax in feature lists where applicable.

Possibly related PRs

  • build: use cargo binstall to speed up builds #2321: The changes in the main PR and the retrieved PR are related as both involve updating the installation command for the wasm-bindgen-cli package to version 0.2.100, specifically in the context of using cargo binstall.
  • build: bump wasm-bindgen to 0.2.99 #2395: The changes in the main PR and the retrieved PR are related as both involve updating the version of the wasm-bindgen-cli package from 0.2.99 to 0.2.100 and from 0.2.86 to 0.2.99, respectively, in the same installation command across different files.
  • chore(release): update change log and release v1.8.0 #2427: The changes in the main PR, which involve updating the version of the wasm-bindgen-cli package in the Dockerfile, are related to the retrieved PR that also updates the version of wasm-bindgen in various files, indicating a direct connection at the code level.

Suggested reviewers

  • QuantumExplorer
  • shumkov

Poem

I'm a little rabbit with a coder's delight,
Hopping through updates from morning to night.
Versions jump from 0.2.99 to 0.2.100 on my trail,
Precision in changes, leaving no detail stale.
With whiskers twitching, I celebrate this code tale! 🐰


🪧 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.
  • @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: 0

🧹 Nitpick comments (2)
Cargo.toml (2)

32-32: Token History Contract Addition with Trailing Comma

The inclusion of "packages/token-history-contract", (with a trailing comma) enhances future maintainability by making it easy to add new members later. Please verify that the corresponding package exists and is configured correctly.


41-44: Intentional Disabling of Tower Patches

The [patch.crates-io] section now has the lines for tower-service, tower-layer, and tower commented out. Confirm that this change is intentional to prevent these patches from being applied. If these patches are no longer needed, you might consider removing them entirely for a cleaner configuration.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 88aec56 and 86e256c.

⛔ Files ignored due to path filters (1)
  • Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (1)
  • Cargo.toml (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (19)
  • GitHub Check: Rust packages (token-history-contract) / Formatting
  • GitHub Check: Rust packages (token-history-contract) / Unused dependencies
  • GitHub Check: Rust packages (rs-dapi-client) / Formatting
  • GitHub Check: Rust packages (rs-dapi-client) / Linting
  • GitHub Check: Rust packages (rs-dapi-client) / Tests
  • GitHub Check: Rust packages (rs-dapi-client) / Check each feature
  • GitHub Check: Rust packages (drive-abci) / Tests
  • GitHub Check: Rust packages (drive-abci) / Check each feature
  • GitHub Check: Rust packages (rs-dapi-client) / Unused dependencies
  • GitHub Check: Rust packages (drive-abci) / Unused dependencies
  • GitHub Check: Rust packages (wasm-dpp) / Unused dependencies
  • GitHub Check: Rust packages (drive-abci) / Linting
  • GitHub Check: Rust packages (dpns-contract) / Linting
  • GitHub Check: Rust packages (wallet-utils-contract) / Tests
  • GitHub Check: Build Docker images (Dashmate helper, dashmate-helper, dashmate-helper) / Build Dashmate helper image
  • GitHub Check: Build Docker images (DAPI, dapi, dapi) / Build DAPI image
  • GitHub Check: Build Docker images (Drive, drive, drive-abci) / Build Drive image
  • GitHub Check: Build JS packages / Build JS
  • GitHub Check: Rust crates security audit

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 86e256c and 98abdd9.

⛔ Files ignored due to path filters (1)
  • Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (8)
  • packages/rs-dpp/Cargo.toml (1 hunks)
  • packages/rs-drive-abci/Cargo.toml (1 hunks)
  • packages/rs-drive-proof-verifier/Cargo.toml (2 hunks)
  • packages/rs-drive/Cargo.toml (3 hunks)
  • packages/rs-platform-serialization/Cargo.toml (1 hunks)
  • packages/rs-platform-value/Cargo.toml (1 hunks)
  • packages/simple-signer/Cargo.toml (1 hunks)
  • packages/strategy-tests/Cargo.toml (1 hunks)
✅ Files skipped from review due to trivial changes (2)
  • packages/rs-dpp/Cargo.toml
  • packages/rs-drive-proof-verifier/Cargo.toml
⏰ Context from checks skipped due to timeout of 90000ms (20)
  • GitHub Check: Rust packages (dpp) / Linting
  • GitHub Check: Rust packages (dpp) / Unused dependencies
  • GitHub Check: Rust packages (dpp) / Formatting
  • GitHub Check: Rust packages (dpp) / Tests
  • GitHub Check: Rust packages (dpp) / Check each feature
  • GitHub Check: Rust packages (dashpay-contract) / Tests
  • GitHub Check: Rust packages (dashpay-contract) / Unused dependencies
  • GitHub Check: Rust packages (dpns-contract) / Linting
  • GitHub Check: Rust packages (dpns-contract) / Formatting
  • GitHub Check: Rust packages (token-history-contract) / Formatting
  • GitHub Check: Rust packages (token-history-contract) / Unused dependencies
  • GitHub Check: Rust packages (token-history-contract) / Linting
  • GitHub Check: Rust packages (rs-dapi-client) / Tests
  • GitHub Check: Rust packages (rs-dapi-client) / Check each feature
  • GitHub Check: Rust packages (rs-dapi-client) / Linting
  • GitHub Check: Rust packages (rs-dapi-client) / Formatting
  • GitHub Check: Build Docker images (DAPI, dapi, dapi) / Build DAPI image
  • GitHub Check: Build Docker images (Dashmate helper, dashmate-helper, dashmate-helper) / Build Dashmate helper image
  • GitHub Check: Build Docker images (Drive, drive, drive-abci) / Build Drive image
  • GitHub Check: Build JS packages / Build JS
🔇 Additional comments (6)
packages/rs-platform-value/Cargo.toml (1)

10-12: Exact version pin for bincode dependency updated.
Enforcing the exact version (=2.0.0-rc.3) for the bincode dependency improves build reproducibility and consistency across the project. Verify that all consumers of this crate are compatible with this specific version.

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

16-18: Bincode version pinned to an exact version.
Locking the bincode dependency to =2.0.0-rc.3 ensures uniform dependency resolution across modules. Confirm that this strict version requirement aligns with downstream integrations.

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

10-12: Bincode dependency updated to an exact version.
Pinning bincode to =2.0.0-rc.3 prevents unintentional upgrades and aids in maintaining consistency between related packages.

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

16-18: Exact bincode version enforced in dependencies.
Changing to =2.0.0-rc.3 for the bincode dependency guarantees strict alignment with the rest of the codebase. Ensure this change is compatible with all integration points.


120-125: Improved formatting for the verify feature list.
Reformatting the verify feature as a multi-line array enhances readability and maintainability without affecting functionality.

packages/simple-signer/Cargo.toml (1)

9-11: Bincode dependency version pin updated.
Specifying =2.0.0-rc.3 for bincode aligns this package with the project-wide dependency management strategy, ensuring consistency across modules.

@lklimek lklimek force-pushed the deps/wasm-bindgen-0.2.100 branch from 34cf457 to 33ab5e1 Compare March 17, 2025 16:14
@shumkov shumkov merged commit 2490558 into v2.0-dev Mar 18, 2025
267 of 268 checks passed
@shumkov shumkov deleted the deps/wasm-bindgen-0.2.100 branch March 18, 2025 01:51
@coderabbitai coderabbitai bot mentioned this pull request Apr 14, 2025
6 tasks
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