Skip to content

chore(release): bump version to 0.1.9#1266

Merged
ctrlc03 merged 2 commits into
mainfrom
chore/v0-1-9
Feb 5, 2026
Merged

chore(release): bump version to 0.1.9#1266
ctrlc03 merged 2 commits into
mainfrom
chore/v0-1-9

Conversation

@ctrlc03

@ctrlc03 ctrlc03 commented Feb 5, 2026

Copy link
Copy Markdown
Collaborator
  • Updated all Rust crates to 0.1.9
  • Updated all npm packages to 0.1.9
  • Updated lock files
  • Generated CHANGELOG.md

Summary by CodeRabbit

  • Documentation

    • Updated changelog for version 0.1.9 with comprehensive list of bug fixes and new features.
  • Chores

    • Released version 0.1.9 across all packages and workspace dependencies.

  - Updated all Rust crates to 0.1.9
  - Updated all npm packages to 0.1.9
  - Updated lock files
  - Generated CHANGELOG.md
@vercel

vercel Bot commented Feb 5, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
crisp Ready Ready Preview, Comment Feb 5, 2026 2:46pm
enclave-docs Ready Ready Preview, Comment Feb 5, 2026 2:46pm

Request Review

@coderabbitai

coderabbitai Bot commented Feb 5, 2026

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Walkthrough

Release version bump from 0.1.8 to 0.1.9 across all workspace and package manifests. Updates CHANGELOG.md with version notes and modifies the version bump script to include subdirectories (examples/CRISP and templates/default) in cargo lock file updates.

Changes

Cohort / File(s) Summary
Release Documentation
CHANGELOG.md
Added new version 0.1.9 entry with bug fixes and features sections detailing changes with issue and commit references.
Cargo Workspace Version
Cargo.toml
Bumped workspace version from 0.1.8 to 0.1.9; updated all 34 e3-\* and related internal dependencies to match new version.
NPM Package Versions
package.json, crates/wasm/package.json, packages/enclave-config/package.json, packages/enclave-contracts/package.json, packages/enclave-react/package.json, packages/enclave-sdk/package.json
Incremented version field from 0.1.8 to 0.1.9 across all NPM package manifests.
Build Script Updates
scripts/bump-versions.ts
Added two additional cargo update commands in updateLockFiles function to process examples/CRISP and templates/default subdirectories.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

Suggested reviewers

  • hmzakhalid
  • cedoor

Poem

🐰 Hop, hop, the versions rise so high,
From eight to nine, beneath the sky,
Each manifest gets its bumpy treat,
Scripts now know where subdirs meet!
A release dance, so fine and spry! 🎉

🚥 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.9' accurately and clearly describes the main change of the pull request—bumping all project versions from 0.1.8 to 0.1.9 across Rust crates, npm packages, and manifests.
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 docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch chore/v0-1-9

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

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

hmzakhalid
hmzakhalid previously approved these changes Feb 5, 2026

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In `@CHANGELOG.md`:
- Around line 1-289: The 0.1.9 changelog entry uses a compare link from v0.1.2
and appears to duplicate the 0.1.8 section; update the "## [0.1.9](...)" compare
URL to point from v0.1.8 to v0.1.9 and replace the duplicated full 0.1.8 content
with only the true delta (new/changed items) for v0.1.9; specifically edit the
header line "## [0.1.9](https://github.com/gnosisguild/enclave/compare/...)" to
use the correct compare range and prune entries that are identical to the v0.1.8
release so the changelog only lists actual 0.1.9 changes.
🧹 Nitpick comments (1)
scripts/bump-versions.ts (1)

325-332: Consider using path.join for path construction.

The new cargo update commands correctly target the self-contained workspaces (examples/CRISP and templates/default), which aligns with the repository's workspace structure where these directories are excluded from the root workspace.

However, for consistency with the rest of the codebase (e.g., line 254, 264, 288) and better cross-platform compatibility, consider using join() from the already-imported path module instead of template string concatenation.

♻️ Suggested refactor
       execSync('cargo update', {
-        cwd: `${this.rootDir}/examples/CRISP`,
+        cwd: join(this.rootDir, 'examples', 'CRISP'),
         stdio: 'pipe',
       })
       execSync('cargo update', {
-        cwd: `${this.rootDir}/templates/default`,
+        cwd: join(this.rootDir, 'templates', 'default'),
         stdio: 'pipe',
       })

Based on learnings: The examples/CRISP directory has its own Cargo.toml workspace configuration, and the root workspace intentionally excludes it to prevent double workspace membership, which is the correct approach for self-contained example workspaces.

Comment thread CHANGELOG.md
@ctrlc03 ctrlc03 merged commit 72b8a94 into main Feb 5, 2026
44 of 45 checks passed
@github-actions github-actions Bot deleted the chore/v0-1-9 branch February 13, 2026 03:18
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