fix(deps): bump jose minimum to ^0.3.5+1#2613
fix(deps): bump jose minimum to ^0.3.5+1#2613neel-sharma wants to merge 2 commits intoGetStream:masterfrom
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✅ Files skipped from review due to trivial changes (2)
📝 WalkthroughWalkthroughThe Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@packages/stream_chat/pubspec.yaml`:
- Line 30: Update the jose dependency constraint from ^0.3.5 to ^0.3.5+1 in the
packages/stream_chat pubspec (change the "jose" entry) to ensure the
CVE-2026-34240 patch is used; also make the identical change to the "jose"
constraint in melos.yaml (the other occurrence mentioned) so both manifests
require the patched 0.3.5+1 or later.
🪄 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: defaults
Review profile: CHILL
Plan: Pro
Run ID: b89415cf-5594-4f53-b079-47b94e80c758
📒 Files selected for processing (2)
melos.yamlpackages/stream_chat/pubspec.yaml
Submit a pull request
Linear: N/A
Github Issue: N/A
CLA
Description of the pull request
jose 0.3.4 has a JWT signature bypass vulnerability tracked as CVE-2026-34240 / GHSA-vm9r-h74p-hg97. The fix is available in jose 0.3.5+.
This PR bumps the lower bound from
^0.3.4to^0.3.5in two files:melos.yamlpackages/stream_chat/pubspec.yamlNo code changes — the jose API is unchanged. The
^constraint still allows anything>=0.3.5 <0.4.0, so nothing else breaks. Only the vulnerable version is excluded from resolution.Testing: Dependency-only change, no logic affected. Verified
pub getresolves cleanly.Screenshots / Videos
N/A — dependency version bump only, no UI changes.
Summary by CodeRabbit