build: add @noble/hashes as devDependency - #1041
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review. 📝 WalkthroughWalkthroughThe package configuration adds ChangesDevelopment dependency update
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~2 minutes Change: Bug fix Suggested reviewers: Merge Risk: ⚪ Minimal · up to The dependency update is compatible with the repository’s exercised Node versions and has no remaining merge-blocking risk. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 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 |
466a88f to
8a4caf9
Compare
Summary
overridesworkaround with an explicit@noble/hashes@^2.0.0devDependencyMissing: @noble/hashes@2.4.0 from lock filesince Dependabot skips optional peer deps when regenerating the lockfileTest plan
Summary by CodeRabbit