chore(release): v0.17.0-rc.2 - #438
Conversation
Aligns Guardian with node 0.16.0-rc.3 (running on devnet), which changed the AccountResponse storage-map proof format that only miden-client rc.3 speaks. Protocol crates stay at 0.16.0-rc.6; the VM/crypto stack moves to 0.29.4 in the lockfile to match the WASM embedded in web SDK rc.5.
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
There was a problem hiding this comment.
Pull request overview
This PR performs the coordinated v0.17.0-rc.2 release bump across the Rust workspace, TypeScript packages, example lockfiles, and published API docs, keeping the repository’s published metadata aligned with the Miden dependency line introduced in the stacked PR #437.
Changes:
- Bump Rust workspace/crate versions and internal exact pins to
0.17.0-rc.2(plus lockfile refresh). - Bump npm package versions to
0.17.0-rc.2and align the@openzeppelin/guardian-clientdependency range used by@openzeppelin/miden-multisig-client. - Update OpenAPI
info.versionfields and extend the Miden compatibility matrix with an0.17.0-rc.2row (while restoring therc.1row to the versions it shipped with).
Reviewed changes
Copilot reviewed 13 out of 20 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| Cargo.toml | Bumps workspace package version to 0.17.0-rc.2. |
| Cargo.lock | Updates workspace crate versions to 0.17.0-rc.2 (and lockfile consistency). |
| crates/client/Cargo.toml | Updates internal pin for guardian-shared to =0.17.0-rc.2. |
| crates/contracts/Cargo.toml | Updates internal pin for guardian-shared to =0.17.0-rc.2. |
| crates/miden-multisig-client/Cargo.toml | Updates internal exact pins (and dev-dep testing pin) to =0.17.0-rc.2. |
| packages/guardian-client/package.json | Bumps package version to 0.17.0-rc.2. |
| packages/guardian-evm-client/package.json | Bumps package version to 0.17.0-rc.2. |
| packages/guardian-operator-client/package.json | Bumps package version to 0.17.0-rc.2. |
| packages/miden-multisig-client/package.json | Bumps package version and updates @openzeppelin/guardian-client dependency range to ^0.17.0-rc.2. |
| packages/package-lock.json | Updates workspace package versions and dependency range metadata to 0.17.0-rc.2. |
| examples/web/package-lock.json | Refreshes workspace-linked package version metadata to 0.17.0-rc.2. |
| examples/smoke-web/package-lock.json | Refreshes workspace-linked package version metadata to 0.17.0-rc.2. |
| examples/operator-smoke-web/package-lock.json | Refreshes workspace-linked package version metadata to 0.17.0-rc.2. |
| examples/evm-smoke-web/package-lock.json | Refreshes workspace-linked package version metadata to 0.17.0-rc.2. |
| examples/_shared/multisig-browser/package-lock.json | Refreshes workspace-linked package version metadata to 0.17.0-rc.2. |
| docs/openapi.json | Updates info.version to 0.17.0-rc.2. |
| docs/openapi-client.json | Updates info.version to 0.17.0-rc.2. |
| docs/openapi-dashboard.json | Updates info.version to 0.17.0-rc.2. |
| docs/openapi-evm.json | Updates info.version to 0.17.0-rc.2. |
| docs/MIDEN_COMPATIBILITY.md | Adds 0.17.0-rc.2 row and restores 0.17.0-rc.1 row to shipped dependency pins. |
Files not reviewed (6)
- examples/_shared/multisig-browser/package-lock.json: Generated file
- examples/evm-smoke-web/package-lock.json: Generated file
- examples/operator-smoke-web/package-lock.json: Generated file
- examples/smoke-web/package-lock.json: Generated file
- examples/web/package-lock.json: Generated file
- packages/package-lock.json: Generated file
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Stacked on #437. Once #437 merges, retarget this PR to
main.Scope
Coordinated SDK release
0.17.0-rc.2. Dependency-only release: nocrates/*/srcorpackages/*/srcchanges sincev0.17.0-rc.1, so package READMEs are unchanged. It ships the Miden dependency alignment from #437 (miden-client0.16.0-rc.3, web SDK0.16.0-rc.5, VM/crypto 0.29.4) against devnet node0.16.0-rc.3.Files
Cargo.tomlworkspace version; internalguardian-shared/guardian-client/miden-confidential-contractsdep pins incrates/client,crates/contracts,crates/miden-multisig-client;Cargo.lock.packages/{guardian-client,guardian-evm-client,miden-multisig-client,guardian-operator-client}/package.jsonversions,miden-multisig-client@openzeppelin/guardian-clientrange^0.17.0-rc.2;packages/package-lock.json(guardian-client stays a workspace link).examples/{web,smoke-web,operator-smoke-web,evm-smoke-web},examples/_shared/multisig-browser) refreshed so theirfile:link metadata matches; version fields only.docs/openapi*.jsoninfo.version;docs/MIDEN_COMPATIBILITY.mdgains an rc.2 row and restores the rc.1 row to what rc.1 actually shipped with (miden-client =0.16.0-rc.2, web SDK0.16.0-rc.3).Validation
cargo test -p guardian-shared -p guardian-client -p miden-confidential-contracts -p miden-multisig-client: all pass.cargo publish --dry-run --lockedfor the four crates: all package.npm ci+ build + test for the four packages: 86 / 10 / 490 / 88 tests pass.npm publish --dry-run --tag rcfor the four packages: all pack at0.17.0-rc.2.Release steps after merge
Publishing the release triggers Publish Rust Crates, Publish NPM Packages (prerelease is tagged
rc), and Docker Publish; approve or decline thereleaseenvironment gate for the server image as appropriate.Summary by CodeRabbit