chore(release): bump version to 0.2.0#1567
Conversation
- Updated all Rust crates to 0.2.0 - Updated all npm packages to 0.2.0 - Updated lock files - Generated CHANGELOG.md
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
More reviews will be available in 8 minutes and 40 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughCoordinated release edits: bumped Cargo workspace and npm package versions to 0.2.0, added a v0.1.15 CHANGELOG entry, updated release and CI workflows (NOIR_TOOLCHAIN, noirup/Nargo, cachix action, NODE_TLS_REJECT_UNAUTHORIZED), adjusted flake.nix cargoLock entries, and tweaked the bump script. ChangesRelease 0.2.0
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested labels
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
- Updated all Rust crates to 0.2.0 - Updated all npm packages to 0.2.0 - Updated lock files - Generated CHANGELOG.md
The fhe.rs bump (#1561) moved fhe/fhe-math to 0.2.0 and fhe-traits/fhe-util to 0.1.1 (git rev a92478b3) but only touched templates/default/flake.nix, leaving the root flake's cargoLock.outputHashes keyed by the old -0.1.0-beta.7 versions. nix build failed with "A hash was specified for fhe-0.1.0-beta.7, but there is no corresponding git dependency". Rename the four keys to match Cargo.lock. NOTE: fheHash (the FOD hash value) still needs updating for the new rev — the next `nix build .#default` will report the correct `got: sha256-...` to paste into flake.nix line 18. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…mplate updateLockFiles() ran bare `cargo update` in examples/CRISP and templates/default, which upgrades all transitive deps to latest and re-floats alloy-sol-type-parser -> 1.6.0 / alloy-tx-macros -> 1.8.3 on every version bump (breaking alloy-dyn-abi 1.3.0 and alloy-consensus 1.0.41). The root already used `cargo update --workspace`; apply the same to the other two workspaces so a bump only refreshes member versions and can't float pinned transitive deps. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
flake.nix (1)
18-18:⚠️ Potential issue | 🟠 Major | ⚡ Quick winUpdate
fheHashto match the new fhe- crate versions.*The
fheHashon line 18 is still set to the hash for the old0.1.0-beta.7versions, but lines 136-139 now reference0.2.0and0.1.1versions. This hash mismatch will cause the Nix build to fail when it attempts to fetch and verify the fhe-* dependencies.As noted in the commit message, run
nix buildto obtain the correct sha256, then update line 18 with the new hash value.Also applies to: 136-139
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@flake.nix` at line 18, The fheHash value is stale for the updated fhe-* crate versions (0.2.0 and 0.1.1); run nix build to get the new sha256 and replace the current fheHash value with the returned hash, and also update any other fhe-related hash entries that correspond to the fhe-* crate versions (the other fhe* hash occurrences that reference 0.2.0 / 0.1.1) so all fhe hashes match the fetched artifacts.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Outside diff comments:
In `@flake.nix`:
- Line 18: The fheHash value is stale for the updated fhe-* crate versions
(0.2.0 and 0.1.1); run nix build to get the new sha256 and replace the current
fheHash value with the returned hash, and also update any other fhe-related hash
entries that correspond to the fhe-* crate versions (the other fhe* hash
occurrences that reference 0.2.0 / 0.1.1) so all fhe hashes match the fetched
artifacts.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 7929eebd-56db-4f58-811e-c7bb87d08ac8
📒 Files selected for processing (2)
.github/workflows/releases.ymlflake.nix
🚧 Files skipped from review as they are similar to previous changes (1)
- .github/workflows/releases.yml
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/ci.yml:
- Around line 677-683: Currently the workflow disables TLS by setting
NODE_TLS_REJECT_UNAUTHORIZED=0 for matrix.test-suite == 'test:sdk'; instead
remove that conditional and implement a secure CRS provisioning: add CI steps to
fetch the CRS once (or restore from a cache/artifact) and verify its integrity
before running tests that call Barretenberg.initSRSChonk (used in
examples/CRISP/.../vote.ts and
packages/enclave-sdk/.../user-data-encryption.ts). Concretely, stop setting
NODE_TLS_REJECT_UNAUTHORIZED to 0, add steps to (a) download the CRS to a known
path and verify against a repo-stored expected hash/signature, or (b) upload the
verified CRS as a workflow artifact/cache and restore it in subsequent runs, and
ensure the test:sdk job uses that verified local CRS file when invoking
initSRSChonk.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 8e178364-f189-4f74-a7ec-df18fa1499fc
📒 Files selected for processing (2)
.github/workflows/ci.ymlscripts/bump-versions.ts
crisp_e2e is a Playwright/Chromium test; the in-page bb.js fetches the public Aztec CRS over HTTPS and CI's browser rejects the served cert as expired (ERR_CERT_DATE_INVALID). NODE_TLS_REJECT_UNAUTHORIZED doesn't apply to the browser, so set ignoreHTTPSErrors + --ignore-certificate-errors on the chromium project. CRS is public, integrity-checked data. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2 participants
Summary by CodeRabbit
Chores
Build / CI