chore: resolve open dependabot security alerts - #399
Conversation
There was a problem hiding this comment.
Code Review
This pull request updates dependencies in the uv.lock file, upgrading aiohttp from 3.13.5 to 3.14.1 along with its corresponding wheels and a conditional dependency on typing-extensions. Additionally, openfeature-provider-flagd is upgraded from 0.4.1 to 0.5.0. As there are no review comments, no further feedback is provided.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #399 +/- ##
==========================================
- Coverage 96.40% 96.28% -0.12%
==========================================
Files 47 47
Lines 1778 1778
==========================================
- Hits 1714 1712 -2
- Misses 64 66 +2 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
Warning Review limit reached
Next review available in: 5 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe flagd provider’s Hatch protobuf build hook now requires protobuf 7.x and pins grpcio-tools to version 1.82.1, aligning build-time tooling with the configured runtime dependencies. ChangesProtobuf tooling alignment
Estimated code review effort: 1 (Trivial) | ~3 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
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 |
ec72952 to
68992aa
Compare
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 `@providers/openfeature-provider-flagd/pyproject.toml`:
- Around line 50-62: Align the runtime dependency constraints with
grpcio-tools==1.82.1 by raising the protobuf floor to >=7.35.1 and the grpcio
floor to >=1.82.1 in the corresponding runtime dependency declarations. Keep the
existing upper bounds and ensure the build-tool and runtime versions remain
compatible.
🪄 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: CHILL
Plan: Pro Plus
Run ID: 0c5fd530-a96a-4abb-961c-5ddb8a9411bc
⛔ Files ignored due to path filters (1)
uv.lockis excluded by!**/*.lock
📒 Files selected for processing (1)
providers/openfeature-provider-flagd/pyproject.toml
- aiohttp 3.13.5 -> 3.14.1 (medium, alerts #34, #35) Signed-off-by: Jonathan Norris <[email protected]>
Signed-off-by: Jonathan Norris <[email protected]>
Signed-off-by: Jonathan Norris <[email protected]>
Signed-off-by: Jonathan Norris <[email protected]>
…ntime Signed-off-by: Jonathan Norris <[email protected]>
grpcio-tools 1.82+ dropped protobuf 6.x support and now requires protobuf>=7.35.1,<8.0.0, so the isolated build hook's protobuf pin must track the runtime protobuf constraint instead of staying on ~=6.0 (see #400 for why it was pinned there originally). Signed-off-by: Jonathan Norris <[email protected]>
Signed-off-by: Todd Baert <[email protected]>
e9ca603 to
45c95e9
Compare
Summary
uv.lock.aiohttpto 3.14.1 (resolves 11 alerts, chore: add CODEOWNERS #34-ModuleNotFoundError when importing flagd provider #44).cryptographyto 49.0.0 (resolves 1 high-severity alert, fix: include proto file in build for openfeature-provider-flagd #45).grpcio/grpcio-health-checkingto 1.82.1 and the isolated build-timegrpcio-toolspin to match, since the runtimegrpcio>=1.81.0constraint had drifted ahead of the previously-pinnedgrpcio-tools, which generates gRPC stubs incompatible with the runtime version at import time (breaking the flagd provider test job).protobufpin (used only by the isolated Hatch protobuf build hook) from~=6.0to>=7.0.0,<8.0.0, matching the runtime constraint.grpcio-tools>=1.82dropped protobuf 6.x support entirely and now requires protobuf 7.35+, so the old 6.x pin (originally added in chore(deps): bump protobuf to 7.35.1 #400 to work around grpcio-tools' pre-release-only protobuf 7 support) no longer resolves.All changes are to transitive dependencies.
aiohttpandgrpciocome in via the provider packages;cryptographyviamoto/aiobotocoreinopenfeature-provider-aws-ssm's dev group. The lockfile was regenerated withuv lock --upgrade-package <pkg>. Verifieduv build,mypy,ruff, and the affected package test suites (flagd, aws-ssm) on the patched versions.Dependabot Alerts Resolved
aiohttpaiohttpaiohttpaiohttpaiohttpaiohttpaiohttpaiohttpaiohttpaiohttpaiohttpcryptography