chore(release): bump version to 0.1.10

[ctrlc03]

• Updated all Rust crates to 0.1.10
• Updated all npm packages to 0.1.10
• Updated lock files
• Generated CHANGELOG.md

Summary by CodeRabbit

• Chores

  • Bumped version to 0.1.10 across all workspace modules and packages.

• Documentation

  • Expanded changelog with comprehensive documentation of bug fixes and features for version 0.1.10, covering enhancements across multiple components.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
crisp	Ready	Preview, Comment	Feb 6, 2026 4:19pm
enclave-docs	Ready	Preview, Comment	Feb 6, 2026 4:19pm

[coderabbitai]

📝 Walkthrough

Walkthrough

This is a release version bump PR that updates the entire workspace from version 0.1.9 to 0.1.10. All version strings in Cargo.toml, multiple package.json files, and workspace dependencies are incremented. A comprehensive CHANGELOG.md entry documents the new version's bug fixes and features.

Changes

Cohort / File(s)	Summary
Changelog CHANGELOG.md	Added comprehensive version 0.1.10 release notes with bug fixes and features sections.
Workspace Version Cargo.toml	Bumped workspace package version and all workspace dependency declarations from 0.1.9 to 0.1.10.
NPM Package Versions crates/wasm/package.json, package.json, packages/enclave-config/package.json, packages/enclave-contracts/package.json, packages/enclave-react/package.json, packages/enclave-sdk/package.json	Updated version field from 0.1.9 to 0.1.10 across all package.json manifests.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• chore(release): bump version to 0.1.9 #1266: Previous version release that bumped workspace from 0.1.8 to 0.1.9 with identical pattern of changelog and manifest updates.
• chore(release): bump version to 0.1.5 #845: Performs the same release-oriented version updates across Cargo.toml, package.json files, and CHANGELOG entries.
• chore(release): bump version to 0.1.3 #779: Release PR performing version bumps and CHANGELOG.md updates across the same set of manifest files.

Suggested reviewers

• hmzakhalid
• cedoor

Poem

🐰 A new release hops into view,
Version 0.1.10, shiny and true!
From tests to fixes, features galore,
The changelog sings of improvements in store.
Bumped versions dance through each file with cheer,
The workspace is ready—let's publish it here! 🚀

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'chore(release): bump version to 0.1.10' accurately and clearly summarizes the main purpose of the pull request, which is to release version 0.1.10 by bumping versions across all components.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/v0-1-10

---

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

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

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@CHANGELOG.md`:
- Around line 1-2: The changelog header currently uses the wrong compare range:
update the header string "##
[0.1.10](https://github.com/gnosisguild/enclave/compare/v0.1.2...v0.1.10)
(2026-02-06)" so the compare link starts from v0.1.9 (e.g. change
.../compare/v0.1.9...v0.1.10) and regenerate or re-run whatever script produced
the section so the commit/PR list reflects changes since v0.1.9 rather than
v0.1.2.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Changelog compare link likely points to the wrong base.
Line 1 compares from v0.1.2, which makes the 0.1.10 entry read like a full history repeat. If this entry should capture changes since 0.1.9, update the compare link (and regenerate the section if needed).

🔧 Proposed header fix

-## [0.1.10](https://github.com/gnosisguild/enclave/compare/v0.1.2...v0.1.10) (2026-02-06)
+## [0.1.10](https://github.com/gnosisguild/enclave/compare/v0.1.9...v0.1.10) (2026-02-06)

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	## [0.1.10](https://github.com/gnosisguild/enclave/compare/v0.1.2...v0.1.10) (2026-02-06)
	## [0.1.10](https://github.com/gnosisguild/enclave/compare/v0.1.9...v0.1.10) (2026-02-06)

🤖 Prompt for AI Agents

In `@CHANGELOG.md` around lines 1 - 2, The changelog header currently uses the
wrong compare range: update the header string "##
[0.1.10](https://github.com/gnosisguild/enclave/compare/v0.1.2...v0.1.10)
(2026-02-06)" so the compare link starts from v0.1.9 (e.g. change
.../compare/v0.1.9...v0.1.10) and regenerate or re-run whatever script produced
the section so the commit/PR list reflects changes since v0.1.9 rather than
v0.1.2.