chore(deps): refresh dependency lockfile

[mpiton]

Summary

• refresh compatible transitive dependencies in Cargo.lock
• keep dependency manifests and major versions unchanged
• use the official Extism crates.io stack

Validation

• cargo fmt and native/WASM clippy passed
• native tests and WASM smoke tests passed
• cargo audit: 0 vulnerabilities

Type

chore

---

Summary by cubic

Refresh Cargo.lock to update transitive dependencies and align with the official Extism crates.io stack. No manifest updates or major version bumps; no API or behavior changes.

• Dependencies

  • Updated to latest compatible patch/minor versions in Cargo.lock.
  • Switched to the official Extism crates on crates.io.
  • Modernized WASM toolchain: wasm-bindgen 0.2.126, wasmparser/wast 0.253.x; removed wasip2/wasip3 and old wit-bindgen artifacts.
  • Notable bumps: rustls 0.23.42, regex 1.13.1, serde_json 1.0.150, js-sys 0.3.103.

• Validation

  • cargo fmt and Clippy (native/WASM) passed.
  • Native tests and WASM smoke tests passed.
  • cargo audit: 0 vulnerabilities.

^{Written for commit 5372dce. Summary will update on new commits.}

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

[coderabbitai]

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.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: f0ea8081-9ede-49d7-bf81-75bf376a0e64

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

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	serde_json@​1.0.149 ⏵ 1.0.150
	regex@​1.12.3 ⏵ 1.13.1

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: cargo zerocopy is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → cargo/extism@1.30.0 → cargo/zerocopy@0.8.54 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/zerocopy@0.8.54. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[cubic-dev-ai]

No issues found across 1 file

_{Re-trigger cubic}