-
Notifications
You must be signed in to change notification settings - Fork 18
release: 0.2.2 #568
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
release: 0.2.2 #568
Conversation
WalkthroughVersion increments from 0.2.1 to 0.2.2 across npm package files and Cargo workspace. Optional dependency versions for platform-specific ephemeral-validator binaries are updated in the npm package. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (3)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (9)
🔇 Additional comments (4)
Comment |
Manual Deploy AvailableYou can trigger a manual deploy of this PR branch to testnet: Alternative: Comment
Comment updated automatically when the PR is synchronized. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
3 files reviewed, 2 comments
| dependencies = [ | ||
| "borsh-derive 0.10.4", | ||
| "hashbrown 0.13.2", | ||
| "hashbrown 0.12.3", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
style: downgrade from hashbrown 0.13.2 to 0.12.3 in borsh dependencies - verify this is intentional
Prompt To Fix With AI
This is a comment left during a code review.
Path: Cargo.lock
Line: 814:814
Comment:
**style:** downgrade from `hashbrown 0.13.2` to `0.12.3` in borsh dependencies - verify this is intentional
How can I resolve this? If you propose a fix, please make it concise.| "log", | ||
| "wasm-bindgen", | ||
| "windows-core 0.61.2", | ||
| "windows-core 0.56.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
style: downgrade from windows-core 0.61.2 to 0.56.0 - verify this is intentional
Prompt To Fix With AI
This is a comment left during a code review.
Path: Cargo.lock
Line: 3006:3006
Comment:
**style:** downgrade from `windows-core 0.61.2` to `0.56.0` - verify this is intentional
How can I resolve this? If you propose a fix, please make it concise.
Summary by CodeRabbit
Greptile Overview
Updated On: 2025-10-12 07:27:32 UTC
Summary
Release version bump from 0.2.1 to 0.2.2 across all workspace packages and NPM distributions.
Key Changes:
Cargo.tomlConcerns:
Cargo.lock:hashbrown(0.13.2→0.12.3) andwindows-core(0.61.2→0.56.0)Confidence Score: 4/5
Cargo.lockdependency downgrades are intentional and don't break compatibilityImportant Files Changed
File Analysis
Sequence Diagram
sequenceDiagram participant Dev as Developer participant CT as Cargo.toml participant NPM as NPM Package Files participant CL as Cargo.lock Files participant CI as CI/CD Pipeline Dev->>CT: Update workspace version to 0.2.2 Dev->>NPM: Update package.json version to 0.2.2 Dev->>NPM: Update package.json.tmpl version to 0.2.2 Dev->>NPM: Update all platform dependencies to 0.2.2 Dev->>CL: Run cargo update CL-->>CL: Regenerate Cargo.lock CL-->>CL: Update all workspace crate versions Note over CL: Side effect: hashbrown 0.13.2→0.12.3 Note over CL: Side effect: windows-core 0.61.2→0.56.0 Dev->>CL: Update test-integration/Cargo.lock CL-->>CL: Update integration test dependencies Dev->>CI: Commit release 0.2.2 CI->>CI: Build and test all platforms CI->>CI: Publish NPM packages CI->>CI: Create release artifacts