fix(deps): Upgrade protobuf to 5.29.6 to fix CVE-2026-0994#93
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe pyproject.toml dependency constraints were simplified: Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 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 |
|
📦 Python package built successfully!
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #93 +/- ##
=======================================
Coverage 74.32% 74.32%
=======================================
Files 94 94
Lines 5535 5535
Branches 824 824
=======================================
Hits 4114 4114
Misses 1155 1155
Partials 266 266
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
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 `@pyproject.toml`:
- Line 63: Update the explicit protobuf dependency constraint in pyproject.toml
so it pins the fixed floor directly: change the existing "protobuf>=4.25.8,<6"
entry to "protobuf>=5.29.6,<6" (and ensure this replaces the standalone protobuf
dependency rather than relying on google-cloud-bigquery-storage's indirect pin);
after editing, regenerate or update lock/constraints files and run the provided
verification script to confirm pyproject.toml and any lock/constraints files now
list the new "protobuf>=5.29.6,<6" constraint and no other looser protobuf
bounds remain.
🪄 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: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: 687206d4-aa57-46c9-b510-d13afc1f4972
⛔ Files ignored due to path filters (1)
poetry.lockis excluded by!**/*.lock
📒 Files selected for processing (1)
pyproject.toml
Unpin google-cloud-bigquery-storage from ==2.16.2 (py<3.13) to >=2.33.1,<3 across all Python versions. This removes the transitive cap that held protobuf at 4.25.x on py3.10–3.12. Set protobuf floor to >=5.29.6,<6 to ensure the fix cannot be regressed by a future dependency change. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
954db1d to
0fedddf
Compare
|
🚀 Review App Deployment Started
|
Unpin google-cloud-bigquery-storage from ==2.16.2 (py<3.13) to
Summary by CodeRabbit