Bump wasm bindgen utils version

[findolor]

Motivation

Solution

Checks

By submitting this for review, I'm confirming I've done the following:

• made this PR as small as possible
• unit-tested any new functionality
• linked any relevant issues or PRs
• included screenshots (if this involves a front-end change)

Summary by CodeRabbit

• Chores
  • Updated the version of an internal dependency to improve compatibility. No impact on features or user experience.

[coderabbitai]

Walkthrough

The version of the wasm-bindgen-utils dependency in the tauri-app/src-tauri/Cargo.toml file was updated from "0.0" to "0.0.8" for the wasm target family. No other changes were made.

Changes

File	Change Summary
tauri-app/src-tauri/Cargo.toml	Updated wasm-bindgen-utils dependency version for wasm target.

Sequence Diagram(s)

No sequence diagram is generated as the change is limited to a dependency version update.

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 911dd38 and 5eed229.

⛔ Files ignored due to path filters (1)

• tauri-app/src-tauri/Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• tauri-app/src-tauri/Cargo.toml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (16)

• GitHub Check: standard-tests (ubuntu-latest, rainix-sol-artifacts)
• GitHub Check: standard-tests (ubuntu-latest, test-js-bindings)
• GitHub Check: standard-tests (ubuntu-latest, rainix-sol-legal)
• GitHub Check: standard-tests (ubuntu-latest, rainix-sol-test)
• GitHub Check: standard-tests (ubuntu-latest, rainix-rs-static)
• GitHub Check: standard-tests (ubuntu-latest, rainix-rs-artifacts, true)
• GitHub Check: standard-tests (ubuntu-latest, rainix-wasm-artifacts)
• GitHub Check: standard-tests (ubuntu-latest, rainix-wasm-test)
• GitHub Check: standard-tests (ubuntu-latest, ob-rs-test, true)
• GitHub Check: standard-tests (ubuntu-latest, rainix-sol-static)
• GitHub Check: test
• GitHub Check: git-clean
• GitHub Check: Deploy-Preview
• GitHub Check: test
• GitHub Check: build-tauri (ubuntu-22.04, true)
• GitHub Check: test

🔇 Additional comments (1)

tauri-app/src-tauri/Cargo.toml (1)

44-44:

Details

✅ Verification successful

Include updated Cargo.lock and verify published version
Bumping wasm-bindgen-utils in Cargo.toml requires running cargo update so that Cargo.lock reflects the new version. Please commit the updated lock file (if you’re tracking it) or document how you’re handling lockfile management. Also verify that 0.0.8 is actually published on crates.io to avoid build failures.

Run the following to check availability and update the lockfile:

---

🏁 Script executed:

#!/bin/bash
# Skip cloning: external crate check
# Verify that version 0.0.8 exists on crates.io
curl -s https://crates.io/api/v1/crates/wasm-bindgen-utils \
  | grep '"num":"0.0.8"' \
  || { echo "Error: wasm-bindgen-utils@0.0.8 not found on crates.io"; exit 1; }

# Update Cargo.lock to pin the new version
cargo update -p wasm-bindgen-utils --precise 0.0.8

Length of output: 11753

---

To verify that the lockfile has been updated with the new wasm-bindgen-utils = "0.0.8" entry, let’s search all Cargo.lock files in the repo and check for the pinned version:

---

🏁 Script executed:

#!/usr/bin/env bash
# Locate Cargo.lock files and check that wasm-bindgen-utils is pinned at 0.0.8
find . -type f -name Cargo.lock | while read lock; do
  echo "== Inspecting $lock =="
  rg -C2 'name = "wasm-bindgen-utils"' -n "$lock" || echo "  → wasm-bindgen-utils not found in $lock"
done

Length of output: 989

---

Cargo.lock updated & crate version confirmed

• wasm-bindgen-utils@0.0.8 is published on crates.io.
• Both Cargo.lock and tauri-app/src-tauri/Cargo.lock now include a version = "0.0.8" entry.

No further action needed.

---

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.

❤️ 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in 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.